From: Qais Yousef <qyousef@layalina.io>
To: Lukasz Luba <lukasz.luba@arm.com>
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
rostedt@goodmis.org, mhiramat@kernel.org, mingo@redhat.com,
peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
bsegall@google.com, mgorman@suse.de, bristot@redhat.com,
vschneid@redhat.com, delyank@fb.com, qyousef@google.com
Subject: Re: [PATCH 1/3] sched/tp: Add new tracepoint to track uclamp set from user-space
Date: Mon, 3 Apr 2023 14:46:06 +0100 [thread overview]
Message-ID: <20230403134606.amdxfmr5fb544xnv@airbuntu> (raw)
In-Reply-To: <20230322151843.14390-2-lukasz.luba@arm.com>
Hi Lukasz!
On 03/22/23 15:18, Lukasz Luba wrote:
> The user-space can set uclamp value for a given task. It impacts task
> placement decisions made by the scheduler. This is very useful information
> and helps to understand the system behavior or track improvements in
> middleware and applications which start using uclamp mechanisms and report
> better performance in tests.
We do have uclamp trace events in sched_tp, why are they not sufficient?
https://github.com/qais-yousef/sched_tp/blob/main/sched_events.h#L233
Do you really want to know the exact time the value has changed?
Would it make sense to introduce a generic sched_setscheduler tracepoint
instead? Although this might not be necessary as I think we can use
register_kprobe() to register a callback and create a new event without any
additional tracepoint. sched_setscheduler() is not inlined so should be easy to
hook into and create events, no?
Thanks
--
Qais Yousef
>
> Signed-off-by: Lukasz Luba <lukasz.luba@arm.com>
> ---
> include/trace/events/sched.h | 4 ++++
> kernel/sched/core.c | 5 +++++
> 2 files changed, 9 insertions(+)
>
> diff --git a/include/trace/events/sched.h b/include/trace/events/sched.h
> index fbb99a61f714..dbfb30809f15 100644
> --- a/include/trace/events/sched.h
> +++ b/include/trace/events/sched.h
> @@ -735,6 +735,10 @@ DECLARE_TRACE(sched_update_nr_running_tp,
> TP_PROTO(struct rq *rq, int change),
> TP_ARGS(rq, change));
>
> +DECLARE_TRACE(uclamp_update_tsk_tp,
> + TP_PROTO(struct task_struct *tsk, int uclamp_id, unsigned int value),
> + TP_ARGS(tsk, uclamp_id, value));
> +
> #endif /* _TRACE_SCHED_H */
>
> /* This part must be outside protection */
> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> index 488655f2319f..882c92e3ccf0 100644
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -110,6 +110,7 @@ EXPORT_TRACEPOINT_SYMBOL_GPL(sched_overutilized_tp);
> EXPORT_TRACEPOINT_SYMBOL_GPL(sched_util_est_cfs_tp);
> EXPORT_TRACEPOINT_SYMBOL_GPL(sched_util_est_se_tp);
> EXPORT_TRACEPOINT_SYMBOL_GPL(sched_update_nr_running_tp);
> +EXPORT_TRACEPOINT_SYMBOL_GPL(uclamp_update_tsk_tp);
>
> DEFINE_PER_CPU_SHARED_ALIGNED(struct rq, runqueues);
>
> @@ -1936,12 +1937,16 @@ static void __setscheduler_uclamp(struct task_struct *p,
> attr->sched_util_min != -1) {
> uclamp_se_set(&p->uclamp_req[UCLAMP_MIN],
> attr->sched_util_min, true);
> + trace_uclamp_update_tsk_tp(p, UCLAMP_MIN,
> + attr->sched_util_min);
> }
>
> if (attr->sched_flags & SCHED_FLAG_UTIL_CLAMP_MAX &&
> attr->sched_util_max != -1) {
> uclamp_se_set(&p->uclamp_req[UCLAMP_MAX],
> attr->sched_util_max, true);
> + trace_uclamp_update_tsk_tp(p, UCLAMP_MAX,
> + attr->sched_util_max);
> }
> }
>
> --
> 2.17.1
>
next prev parent reply other threads:[~2023-04-03 13:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 15:18 [PATCH 0/3] Add basic tracing for uclamp and schedutil Lukasz Luba
2023-03-22 15:18 ` [PATCH 1/3] sched/tp: Add new tracepoint to track uclamp set from user-space Lukasz Luba
2023-04-03 13:46 ` Qais Yousef [this message]
2023-04-03 16:47 ` Lukasz Luba
2023-04-04 17:17 ` Qais Yousef
2023-04-05 10:50 ` Lukasz Luba
2023-03-22 15:18 ` [PATCH 2/3] cpufreq: schedutil: Refactor sugov_update_shared() internals Lukasz Luba
2023-03-22 15:18 ` [PATCH 3/3] schedutil: trace: Add tracing to capture filter out requests Lukasz Luba
2023-03-22 17:37 ` kernel test robot
2023-04-03 13:46 ` Qais Yousef
2023-04-03 17:02 ` Lukasz Luba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230403134606.amdxfmr5fb544xnv@airbuntu \
--to=qyousef@layalina.io \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=delyank@fb.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=mgorman@suse.de \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=qyousef@google.com \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®