From: Changwoo Min <changwoo@igalia.com>
To: Tejun Heo <tj@kernel.org>
Cc: void@manifault.com, arighi@nvidia.com, kernel-dev@igalia.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched_ext: Add trace point to track sched_ext core events
Date: Thu, 27 Feb 2025 16:41:46 +0900 [thread overview]
Message-ID: <7d985c1a-1e4a-4518-917d-4ff701d7bb9e@igalia.com> (raw)
In-Reply-To: <Z79ivCISjmFlkecF@slm.duckdns.org>
Hi Tejun,
On 25. 2. 27. 03:51, Tejun Heo wrote:
> Hello,
>
> On Wed, Feb 26, 2025 at 11:33:27PM +0900, Changwoo Min wrote:
>> Add tracing support, which may be useful for debugging sched_ext schedulers
>> that trigger a certain event.
>>
>> Signed-off-by: Changwoo Min <changwoo@igalia.com>
>> ---
>> include/trace/events/sched_ext.h | 21 +++++++++++++++++++++
>> kernel/sched/ext.c | 4 ++++
>> 2 files changed, 25 insertions(+)
>>
>> diff --git a/include/trace/events/sched_ext.h b/include/trace/events/sched_ext.h
>> index fe19da7315a9..88527b9316de 100644
>> --- a/include/trace/events/sched_ext.h
>> +++ b/include/trace/events/sched_ext.h
>> @@ -26,6 +26,27 @@ TRACE_EVENT(sched_ext_dump,
>> )
>> );
>>
>> +TRACE_EVENT(sched_ext_add_event,
>> + TP_PROTO(const char *name, int offset, __u64 added),
>> + TP_ARGS(name, offset, added),
>
> Can we do sched_ext_event with @delta? Otherwise, looks fine to me.
Sure, @delta is clearer. I will change it as suggested.
Regards,
Changwoo Min
next prev parent reply other threads:[~2025-02-27 7:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 14:33 Changwoo Min
2025-02-26 18:51 ` Tejun Heo
2025-02-27 7:41 ` Changwoo Min [this message]
2025-02-26 19:15 ` Mukesh Kumar Chaurasiya
2025-02-27 7:38 ` Andrea Righi
2025-02-27 8:05 ` Changwoo Min
2025-02-27 8:19 ` Andrea Righi
2025-02-27 10:23 ` Changwoo Min
2025-02-27 10:55 ` Andrea Righi
2025-02-27 14:21 ` Changwoo Min
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=7d985c1a-1e4a-4518-917d-4ff701d7bb9e@igalia.com \
--to=changwoo@igalia.com \
--cc=arighi@nvidia.com \
--cc=kernel-dev@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=void@manifault.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®