From: Peter Zijlstra <peterz@infradead.org>
To: Valentin Schneider <vschneid@redhat.com>
Cc: "Leonardo Brás" <leobras@redhat.com>,
"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, 4 May 2023 17:01:13 +0200 [thread overview]
Message-ID: <20230504150113.GB1744142@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <xhsmh7ctojoia.mognet@vschneid.remote.csb>
On Thu, May 04, 2023 at 12:59:41PM +0100, Valentin Schneider wrote:
> With that said, I suppose this could still be helpful for e.g. osnoise to
> hook into and point the finger at which CPU/context sent the problematic
> IPI. Or more generally, as Leonardo suggested, to measure CSD IPI delivery
> times.
>
> One thing though is that trace_ipi_send_cpu*() is not used solely for
> CSD's, cf. irq_work_raise() or smp_send_reschedule(). We might want to
> split that into e.g. trace_csd_queue_cpu*() + trace_ipi_send*().
>
> Something like so...
>
Yeah, looks about right I suppose.. it generates more events, but given
we need the csd that's inevitable.
next prev parent reply other threads:[~2023-05-04 15:02 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 [this message]
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
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=20230504150113.GB1744142@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--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=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=thunder.leizhen@huawei.com \
--cc=vschneid@redhat.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®