From: Steven Rostedt <rostedt@goodmis.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Junxuan Liao <ljx@cs.wisc.edu>,
Frederic Weisbecker <frederic@kernel.org>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: Re: Interface for enabling context tracking
Date: Thu, 10 Apr 2025 15:32:44 -0400 [thread overview]
Message-ID: <20250410153244.6b20e328@gandalf.local.home> (raw)
In-Reply-To: <a9d1144e-0f75-4594-b85f-d66b1de623a0@paulmck-laptop>
On Thu, 10 Apr 2025 12:10:19 -0700
"Paul E. McKenney" <paulmck@kernel.org> wrote:
> There is some in-kernel support for turning the rcu_nocbs portion
> of nohz_full on and off on a per-CPU basis, but a given CPU must be
> offline in order to do this transition. Last I heard, there are still
> issues preventing this support from being generalized to cover all of
> the nohz_full functionality, and I doubt that it would be exposed to
> user level until all of nohz_full is supported.
>
> The rcu_nocbs in-kernel functionality is tested regularly.
>
> Are you interested in working on joining the noble quest of getting the
> rest of the nohz_full support in place? (Full disclosure: This stuff
> is non-trivial.)
I believe the request is more of just tracing entry and exit from the
kernel, which just needs a simple trace event at the border crossings.
NOHZ_FULL is to allow the kernel infrastructure to know that a CPU has
transitioned states (no need to do RCU or have a tick on that CPU). That's
a much harder task as you not only need to know the border crossings, you
also need to make sure nothing happens from the locations you mark and the
crossing takes place. That's a much more difficult task.
-- Steve
next prev parent reply other threads:[~2025-04-10 19:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 18:51 Interface for enabling context tracking Junxuan Liao
2025-04-10 19:05 ` Steven Rostedt
2025-04-10 20:31 ` Junxuan Liao
2025-04-17 19:10 ` Junxuan Liao
2025-04-17 20:34 ` Steven Rostedt
2025-04-10 19:10 ` Paul E. McKenney
2025-04-10 19:32 ` Steven Rostedt [this message]
2025-04-11 17:41 ` Junxuan Liao
2025-04-11 21:51 ` Frederic Weisbecker
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=20250410153244.6b20e328@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=ljx@cs.wisc.edu \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=paulmck@kernel.org \
/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