From: Metin Kaya <metin.kaya@arm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, John Stultz <jstultz@google.com>,
Joel Fernandes <joelaf@google.com>,
Qais Yousef <qyousef@google.com>, Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Valentin Schneider <vschneid@redhat.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Ben Segall <bsegall@google.com>,
Zimuzo Ezeozue <zezeozue@google.com>,
Youssef Esmat <youssefesmat@google.com>,
Mel Gorman <mgorman@suse.de>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Will Deacon <will@kernel.org>, Waiman Long <longman@redhat.com>,
Boqun Feng <boqun.feng@gmail.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
Xuewen Yan <xuewen.yan94@gmail.com>,
K Prateek Nayak <kprateek.nayak@amd.com>,
Thomas Gleixner <tglx@linutronix.de>,
kernel-team@android.com, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH] sched: Add trace events for Proxy Execution (PE)
Date: Wed, 21 Feb 2024 14:24:59 +0000 [thread overview]
Message-ID: <10e83b13-bce5-4544-8923-1ee90a2135a8@arm.com> (raw)
In-Reply-To: <20240221092309.00432f37@gandalf.local.home>
On 21/02/2024 2:23 pm, Steven Rostedt wrote:
> On Fri, 2 Feb 2024 08:33:38 +0000
> Metin Kaya <metin.kaya@arm.com> wrote:
>
>> Add sched_[start, finish]_task_selection trace events to measure the
>> latency of PE patches in task selection.
>>
>> Moreover, introduce trace events for interesting events in PE:
>> 1. sched_pe_enqueue_sleeping_task: a task gets enqueued on wait queue of
>> a sleeping task (mutex owner).
>> 2. sched_pe_cross_remote_cpu: dependency chain crosses remote CPU.
>> 3. sched_pe_task_is_migrating: mutex owner task migrates.
>>
>> New trace events can be tested via this command:
>> $ perf trace \
>> -e sched:sched_start_task_selection \
>> -e sched:sched_finish_task_selection \
>> -e sched:sched_pe_enqueue_sleeping_task \
>> -e sched:sched_pe_cross_remote_cpu \
>> -e sched:sched_pe_task_is_migrating
>>
>> Notes:
>> 1. These trace events are not intended to merge upstream. Instead, they
>> are only for making PE tests easier and will be converted to trace
>> points once PE patches hit upstream.
>
> I wonder if the tracepoints should be added though? That is, not adding the
> trace_events that show up in tracefs, but just the tracepoints so that bpf
> or local modules could hook to them?
Yep, the intention is providing necessary support for modules (e.g.,
https://github.com/ARM-software/lisa/blob/main/lisa/_assets/kmodules/lisa/tp.c).
>
> -- Steve
>
>
>> 2. This patch is based on John's Proxy Execution v7 patch series (see
>> the link below) which is also available at
>> https://github.com/johnstultz-work/linux-dev/commits/proxy-exec-v7-6.7-rc6/.
>>
>> Link: https://lore.kernel.org/linux-kernel/CANDhNCrHd+5twWVNqBAhVLfhMhkiO0KjxXBmwVgaCD4kAyFyWw@mail.gmail.com/
>
prev parent reply other threads:[~2024-02-21 14:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 8:33 [PATCH] sched: Add trace events for Proxy Execution (PE) Metin Kaya
2024-02-21 14:23 ` Steven Rostedt
2024-02-21 14:24 ` Metin Kaya [this message]
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=10e83b13-bce5-4544-8923-1ee90a2135a8@arm.com \
--to=metin.kaya@arm.com \
--cc=boqun.feng@gmail.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=joelaf@google.com \
--cc=jstultz@google.com \
--cc=juri.lelli@redhat.com \
--cc=kernel-team@android.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mgorman@suse.de \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=qyousef@google.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=will@kernel.org \
--cc=xuewen.yan94@gmail.com \
--cc=youssefesmat@google.com \
--cc=zezeozue@google.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;
as well as URLs for NNTP newsgroup(s).