From: Valentin Schneider <vschneid@redhat.com>
To: "Leonardo Brás" <leobras@redhat.com>,
"Peter Zijlstra" <peterz@infradead.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Yury Norov <yury.norov@gmail.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Nadav Amit <namit@vmware.com>,
Zhen Lei <thunder.leizhen@huawei.com>,
Chen Zhongjin <chenzhongjin@huawei.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
Marcelo Tosatti <mtosatti@redhat.com>,
Daniel Bristot de Oliveira <bristot@kernel.org>
Subject: Re: [RFC PATCH 1/1] smp: Add tracepoints for functions called with smp_call_function*()
Date: Thu, 11 May 2023 09:13:27 +0100 [thread overview]
Message-ID: <xhsmhv8gzi8uw.mognet@vschneid.remote.csb> (raw)
In-Reply-To: <f96442e9166e4f73be772656a93c89093eddbb8b.camel@redhat.com>
On 10/05/23 17:27, Leonardo Brás wrote:
> On Thu, 2023-05-04 at 12:59 +0100, Valentin Schneider wrote:
>> +TRACE_EVENT(csd_queue_cpu,
>> +
>> + TP_PROTO(const unsigned int cpu,
>> + unsigned long callsite,
>> + smp_call_func_t func,
>> + call_single_data_t *csd),
>> +
>> + TP_ARGS(cpu, callsite, func, csd),
>> +
>> + TP_STRUCT__entry(
>> + __field(unsigned int, cpu)
>> + __field(void *, callsite)
>> + __field(void *, func)
>> + __field(void *, csd)
>> + ),
>> +
>> + TP_fast_assign(
>> + __entry->cpu = cpu;
>> + __entry->callsite = (void *)callsite;
>> + __entry->func = func;
>> + __entry->csd = csd;
>> + ),
>> +
>> + TP_printk("cpu=%u callsite=%pS func=%pS csd=%p",
>> + __entry->cpu, __entry->callsite, __entry->func, __entry->csd)
>> +);
>
> This is for the caller side, right?
>
Yep, see usage lower down.
>> +
>> +DECLARE_EVENT_CLASS(csd_function,
>> +
>> + TP_PROTO(smp_call_func_t func, call_single_data_t *csd),
>> +
>> + TP_ARGS(func, csd),
>> +
>> + TP_STRUCT__entry(
>> + __field(void *, func)
>> + __field(void *, csd)
>> + ),
>> +
>> + TP_fast_assign(
>> + __entry->func = func;
>> + __entry->csd = csd;
>> + ),
>> +
>> + TP_printk("func=%pS csd=%p", __entry->func, __entry->csd)
>> +);
>> +
>> +DEFINE_EVENT(csd_function, csd_function_entry,
>> + TP_PROTO(smp_call_func_t func, call_single_data_t *csd),
>> + TP_ARGS(func, csd)
>> +);
>> +
>> +DEFINE_EVENT(csd_function, csd_function_exit,
>> + TP_PROTO(smp_call_func_t func, call_single_data_t *csd),
>> + TP_ARGS(func, csd)
>> +);
>
> Oh, this is what event_class is for. Thanks for the example :)
>
>> +
>> +#endif /* _TRACE_SMP_H */
>> +
>> +/* This part must be outside protection */
>> +#include <trace/define_trace.h>
>> diff --git a/kernel/smp.c b/kernel/smp.c
>> index ab3e5dad6cfe9..7d28db303e9bc 100644
>> --- a/kernel/smp.c
>> +++ b/kernel/smp.c
>> @@ -27,6 +27,9 @@
>> #include <linux/jump_label.h>
>>
>> #include <trace/events/ipi.h>
>> +#define CREATE_TRACE_POINTS
>> +#include <trace/events/smp.h>
>> +#undef CREATE_TRACE_POINTS
>>
>> #include "smpboot.h"
>> #include "sched/smp.h"
>> @@ -121,6 +124,14 @@ send_call_function_ipi_mask(struct cpumask *mask)
>> arch_send_call_function_ipi_mask(mask);
>> }
>>
>> +static __always_inline void
>> +csd_do_func(smp_call_func_t func, void *info, call_single_data_t *csd)
>> +{
>> + trace_csd_function_entry(func, csd);
>> + func(info);
>> + trace_csd_function_exit(func, csd);
>> +}
>> +
>
> Good one, a helper to avoid calling those traces everywhere.
>
> Honest question:
> Since info == csd->info and func == csd->func, we could just pass csd, right?
> I suppose the suggestion on the 3-argument version is to use the values already
> fetched from memory instead of fetching them again. Is that correct?
>
There's also the special case of CSD_TYPE_TTWU where there is no csd->func,
instead we have an implicit func mapping to sched_ttwu_pending). I think
it's preferable to directly feed the right things to the TP than to
duplicate the "decoding" logic against the *csd passed as TP argument.
next prev parent reply other threads:[~2023-05-11 8:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 7:57 Leonardo Bras
2023-04-06 8:15 ` Sebastian Andrzej Siewior
2023-04-06 8:42 ` Leonardo Brás
2023-04-06 13:49 ` Steven Rostedt
2023-04-19 4:04 ` Leonardo Brás
2023-04-06 9:55 ` Peter Zijlstra
2023-04-19 3:45 ` Leonardo Brás
2023-05-03 4:23 ` Leonardo Brás
2023-05-03 14:59 ` Peter Zijlstra
2023-05-03 15:53 ` Leonardo Bras Soares Passos
2023-05-04 11:59 ` Valentin Schneider
2023-05-04 13:34 ` Steven Rostedt
2023-05-04 15:01 ` Peter Zijlstra
2023-05-10 20:27 ` Leonardo Brás
2023-05-10 22:18 ` Leonardo Bras Soares Passos
2023-05-10 23:05 ` Leonardo Bras Soares Passos
2023-05-11 8:13 ` Valentin Schneider [this message]
2023-05-11 9:25 ` Leonardo Bras Soares Passos
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=xhsmhv8gzi8uw.mognet@vschneid.remote.csb \
--to=vschneid@redhat.com \
--cc=bigeasy@linutronix.de \
--cc=bristot@kernel.org \
--cc=chenzhongjin@huawei.com \
--cc=leobras@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mtosatti@redhat.com \
--cc=namit@vmware.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=thunder.leizhen@huawei.com \
--cc=yury.norov@gmail.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®