From: Valentin Schneider <vschneid@redhat.com>
To: Leonardo Bras <leobras@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Leonardo Bras <leobras@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
Juergen Gross <jgross@suse.com>,
Yury Norov <yury.norov@gmail.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v5 1/2] trace,smp: Add tracepoints around remotelly called functions
Date: Thu, 15 Jun 2023 17:42:36 +0100 [thread overview]
Message-ID: <xhsmh5y7oy8w3.mognet@vschneid.remote.csb> (raw)
In-Reply-To: <20230615065944.188876-5-leobras@redhat.com>
On 15/06/23 03:59, Leonardo Bras wrote:
> The recently added ipi_send_{cpu,cpumask} tracepoints allow finding sources
> of IPIs targeting CPUs running latency-sensitive applications.
>
> For NOHZ_FULL CPUs, all IPIs are interference, and those tracepoints are
> sufficient to find them and work on getting rid of them. In some setups
> however, not *all* IPIs are to be suppressed, but long-running IPI
> callbacks can still be problematic.
>
> Add a pair of tracepoints to mark the start and end of processing a CSD IPI
> callback, similar to what exists for softirq, workqueue or timer callbacks.
>
> Signed-off-by: Leonardo Bras <leobras@redhat.com>
Tested-and-reviewed-by: Valentin Schneider <vschneid@redhat.com>
next prev parent reply other threads:[~2023-06-15 16:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 6:59 [RFC PATCH v5 0/2] trace,smp: Add tracepoints for csd Leonardo Bras
2023-06-15 6:59 ` [RFC PATCH v5 1/2] trace,smp: Add tracepoints around remotelly called functions Leonardo Bras
2023-06-15 16:42 ` Valentin Schneider [this message]
2023-06-19 10:49 ` [tip: smp/core] " tip-bot2 for Leonardo Bras
2023-06-15 6:59 ` [RFC PATCH v5 2/2] trace,smp: Add tracepoints for scheduling " Leonardo Bras
2023-06-15 16:42 ` Valentin Schneider
2023-06-19 10:49 ` [tip: smp/core] " tip-bot2 for Leonardo Bras
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=xhsmh5y7oy8w3.mognet@vschneid.remote.csb \
--to=vschneid@redhat.com \
--cc=bigeasy@linutronix.de \
--cc=jgross@suse.com \
--cc=leobras@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--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®