Messages in this thread | | | From | Lukasz Luba <> | Subject | [RESEND][PATCH v2 0/3] Add basic tracing for uclamp and schedutil | Date | Mon, 22 May 2023 15:56:59 +0100 |
| |
Hi all,
The task scheduler feature: Uclamp, begins to take off. To better understand the dynamics in the task scheduler and CPU frequency requests we need some better tracing. In schedutil (cpufreq governor) we allow to enter the scheduler and make the frequency change. Although, there is some limit in regards to how often this can happen. That min period is provided by the cpufreq driver. Thus, some of the cpufreq requests might be filter out and the frequency won't be changed (hopefuly will be set a bit later). We would like to know about those situations, especially in context of the user-space hints made via Uclamp for particular tasks. This patch set aims to add base for our toolkits and post-processing trace analyzes.
Changelog: v2: - solved the issue from CI build warning, dropped schedutil.h and re-used the sched.h which is available in build_utility.c where cpufreq_schedutil.c is included - added tag for the last patch 3/3 for the CI robot helping hend - re-based on top of v6.4-rc1 v1: - implementation can be found here [1]
Regards, Lukasz Luba
[1] https://lore.kernel.org/lkml/20230322151843.14390-1-lukasz.luba@arm.com/
Lukasz Luba (3): sched/tp: Add new tracepoint to track uclamp set from user-space cpufreq: schedutil: Refactor sugov_update_shared() internals schedutil: trace: Add tracing to capture filter out requests
include/trace/events/sched.h | 8 ++++++++ kernel/sched/core.c | 5 +++++ kernel/sched/cpufreq_schedutil.c | 28 ++++++++++++++++++---------- 3 files changed, 31 insertions(+), 10 deletions(-)
-- 2.25.1
| |