From: Steven Rostedt <rostedt@goodmis.org>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Joel Fernandes <joel@joelfernandes.org>
Subject: Re: [PATCH] tracing: Make tracepoint lockdep check actually test something
Date: Fri, 10 Mar 2023 10:44:58 -0500 [thread overview]
Message-ID: <20230310104458.4f3b1343@gandalf.local.home> (raw)
In-Reply-To: <20230310172758.38c1ec9c6272e41a579ff820@kernel.org>
On Fri, 10 Mar 2023 17:27:58 +0900
Masami Hiramatsu (Google) <mhiramat@kernel.org> wrote:
> This check has been introduced by commit 3a630178fd5f ("tracing: generate RCU
> warnings even when tracepoints are disabled"), and it also added a comment
> above this macro.
>
> * When lockdep is enabled, we make sure to always do the RCU portions of
> * the tracepoint code, regardless of whether tracing is on. However,
> * don't check if the condition is false, due to interaction with idle
> * instrumentation. This lets us find RCU issues triggered with tracepoints
> * even when this tracepoint is off. This code has no purpose other than
> * poking RCU a bit.
>
> I think at least the last sentence will be outdated by this fix.
Ah thanks, I forgot to update that part. What about:
* When lockdep is enabled, we make sure to always test if RCU is
* "watching" regardless if the tracepoint is enabled or not. Tracepoints
* require RCU to be active, and it should always warn at the tracepoint
* site if it is not watching, as it will need to be active when the
* tracepoint is enabled.
?
-- Steve
prev parent reply other threads:[~2023-03-10 15:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 21:56 [PATCH] tracing: Make tracepoint lockdep check actually test something Steven Rostedt
2023-03-10 8:27 ` Masami Hiramatsu
2023-03-10 15:44 ` Steven Rostedt [this message]
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=20230310104458.4f3b1343@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=dave.hansen@linux.intel.com \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.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