[LTP] 回覆: [PATCH] perf_event_open02: set process as RT during Setup stage

[Kuan-ying Zhu (朱冠穎)]

Hi,

Because in mobile products, power consumption requirements may cause the CPU to enter a temporary isolation state (CPU is active but tasks are not assigned) to save power. At this time, task affinity may fail. Therefore, to avoid testing errors caused by power-saving features related to this issue in embedded devices, this suggestion is proposed.

Kuan-ying.Zhu
Kuan-ying.Zhu@mediatek.com

________________________________
寄件者: Cyril Hrubis
已傳送: 星期二, 2025 年 3 月 18 日 下午 07:19
收件者: Edward Liaw
副本: ltp@lists.linux.it; Kuan-ying Zhu (朱冠穎); kernel-team@android.com
主旨: Re: [LTP] [PATCH] perf_event_open02: set process as RT during Setup stage


External email : Please do not click links or open attachments until you have verified the sender or the content.


Hi!
> Move the action of set the task RT from the Verify stage to the Setup
> stage. Avoid potential risks of task migration due to scheduler policy.

What exactly goes wrong if we switch to the realtime policy later? I
see that we do bench_work(500) at the start of the setup. That may mean
that we may get different estimate on how many loops we do per second,
but that would only mean that the test would run for shorter time.

We also do bind_to_current_cpu() just after that, the task shouldn't be
migrated after that.

The actual change looks reasonable, however the patch description should
tell why we need to do this change.

--
Cyril Hrubis
chrubis@suse.cz