Re: [GIT PULL] RCU changes for v3.3

From: Paul E. McKenney
Date: Tue Jan 24 2012 - 14:23:24 EST


On Tue, Jan 24, 2012 at 06:04:17PM +0100, Frederic Weisbecker wrote:
> On Tue, Jan 24, 2012 at 08:53:13AM -0800, Paul E. McKenney wrote:
> > On Tue, Jan 24, 2012 at 05:25:12PM +0100, Eric Dumazet wrote:
> > > Le jeudi 05 janvier 2012 à 14:54 +0100, Ingo Molnar a écrit :
> > > > Linus,
> > > >
> > > > Please pull the latest core-rcu-for-linus git tree from:
> > > >
> > > > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git core-rcu-for-linus
> > > >
> > > > Thanks,
> > >
> > > Hi guys
> > >
> > > New lockdep warning here :
> >
> > Hmmm... Looks like tracing from within the inner idle loop.
> >
> > Because RCU ignores CPUs in the inner idle loop (after the call to
> > rcu_idle_enter()), RCU read-side critical sections are not legal there.
> >
> > One approach would be to delay the call to rcu_idle_enter() until after
> > the tracing is done, and to ensure that the call to rcu_idle_exit() happens
> > before any tracing. I am not seeing perf_trace_power(), so need to
> > update and look again. Or are you looking at -next rather than mainline?
>
> perf_trace_power() is automatically generated by include/trace/ftrace.h
> This is a tracepoint handler so we don't need to worry about it. The problem
> is the call to the tracepoint itself.

Agreed. I was just naively expecting "git grep perf_trace_power" to show
me the call points. :-(

Thanx, Paul

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/