[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200219190521.GO2935@paulmck-ThinkPad-P72>
Date: Wed, 19 Feb 2020 11:05:21 -0800
From: "Paul E. McKenney" <paulmck@...nel.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Peter Zijlstra <peterz@...radead.org>,
linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
mingo@...nel.org, joel@...lfernandes.org,
gregkh@...uxfoundation.org, gustavo@...eddedor.com,
tglx@...utronix.de, josh@...htriplett.org,
mathieu.desnoyers@...icios.com, jiangshanlai@...il.com,
luto@...nel.org, tony.luck@...el.com, frederic@...nel.org,
dan.carpenter@...cle.com, mhiramat@...nel.org
Subject: Re: [PATCH v3 13/22] tracing: Remove regular RCU context for
_rcuidle tracepoints (again)
On Wed, Feb 19, 2020 at 01:00:12PM -0500, Steven Rostedt wrote:
> On Wed, 19 Feb 2020 09:40:25 -0800
> "Paul E. McKenney" <paulmck@...nel.org> wrote:
>
> > > Correct, and if rcuidle is not set, and this is a macro, the SRCU
> > > portion is compiled out.
> >
> > Sigh! Apologies for the noise!
> >
> > If we are using SRCU, we don't care whether or not RCU is watching. OK,
> > maybe finally catching up -- the whole point was use of RCU in other
> > tracing code, wasn't it?
>
> Some callbacks (namely perf) might use RCU, but then the callbacks
> need to make sure rcu is watching.
Got it, thank you!
Thanx, Paul
Powered by blists - more mailing lists