linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: paulmck@linux.vnet.ibm.com
Cc: "Ingo Molnar" <mingo@elte.hu>,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	"Frédéric Weisbecker" <fweisbec@gmail.com>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
	"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] RCU changes for v3.3
Date: Tue, 24 Jan 2012 18:13:28 +0100	[thread overview]
Message-ID: <1327425208.7231.26.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC> (raw)
In-Reply-To: <20120124165312.GG2531@linux.vnet.ibm.com>

Le mardi 24 janvier 2012 à 08:53 -0800, Paul E. McKenney a écrit :
> 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?
> 

I am using mainline, not -next

It seems "powertop" triggers the warnings.

Check include/trace/events/power.h line 75 :

DECLARE_EVENT_CLASS(power,

This declares perf_trace_power()...

include/trace/ftrace.h line 718

#define DECLARE_EVENT_CLASS(call, proto, args, tstruct, assign, print)  \
static notrace void							\
perf_trace_##call(void *__data, proto) ...


Thanks



  parent reply	other threads:[~2012-01-24 17:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-05 13:54 [GIT PULL] RCU changes for v3.3 Ingo Molnar
2012-01-24 16:25 ` Eric Dumazet
2012-01-24 16:53   ` Paul E. McKenney
2012-01-24 17:04     ` Frederic Weisbecker
2012-01-24 19:09       ` Paul E. McKenney
2012-01-24 17:13     ` Eric Dumazet [this message]
2012-01-24 19:41       ` Paul E. McKenney
2012-01-24 19:57         ` Eric Dumazet
2012-01-24 21:11           ` Paul E. McKenney
2012-01-24 22:07             ` Mark Brown
2012-01-24 22:43               ` Paul E. McKenney
2012-01-24 23:51                 ` Mark Brown
2012-01-25  1:36                   ` Paul E. McKenney
2012-01-25 11:59                     ` Mark Brown
2012-01-24 23:29             ` Paul E. McKenney
2012-01-24 23:46               ` Eric Dumazet
2012-01-24 23:54                 ` Paul E. McKenney
2012-03-07 11:44               ` Sergey Senozhatsky
2012-03-07 14:09                 ` Josh Boyer
2012-03-07 15:27                   ` Paul E. McKenney
2012-03-07 15:49                     ` Josh Boyer
2012-03-08 21:26                       ` Paul E. McKenney

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=1327425208.7231.26.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC \
    --to=eric.dumazet@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).