mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Josh Boyer <jwboyer@gmail.com>
Cc: "Sergey Senozhatsky" <sergey.senozhatsky@gmail.com>,
	"Eric Dumazet" <eric.dumazet@gmail.com>,
	"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>,
	Andre@jasper.es
Subject: Re: [GIT PULL] RCU changes for v3.3
Date: Thu, 8 Mar 2012 13:26:47 -0800	[thread overview]
Message-ID: <20120308212647.GV2348@linux.vnet.ibm.com> (raw)
In-Reply-To: <CA+5PVA7q03ZTLtFZH98KvtLbreSx65uGEBJmT02-vCHgogHaMg@mail.gmail.com>

On Wed, Mar 07, 2012 at 10:49:26AM -0500, Josh Boyer wrote:
> On Wed, Mar 7, 2012 at 10:27 AM, Paul E. McKenney
> <paulmck@linux.vnet.ibm.com> wrote:
> > On Wed, Mar 07, 2012 at 09:09:39AM -0500, Josh Boyer wrote:
> >> On Wed, Mar 7, 2012 at 6:44 AM, Sergey Senozhatsky
> >> <sergey.senozhatsky@gmail.com> wrote:
> >> > Hello,
> >> > I just hit the same problem.
> >> >
> >> > Is this patch scheduled for 3.3 until release or will land during 3.4
> >> > merge window?
> >>
> >> There are 3 patches in Paul's 3.4 queue, and another 9 of Steven Rostedt's
> >> that fix this.  They'll wind up in 3.4.
> >>
> >> I looked at reverting the patch that adds this new warning and it doesn't
> >> trivially revert.
> >
> > What are you based on?  I should be able to disable the warning for
> > you easily enough.
> 
> 3.3.  I think I tried reverting 00f49e5729af602deb559b0cf293a00b625e8636 and
> it failed.  Then I locally commented out the WARN_ONCE in the functions which
> got rid of that, but we still get a 'suspicious RCU usage' warning when
> running powertop.  I gave up after that, since it all goes away if we disable
> the debugging options and you have fixes queued for 3.4.

How about the following?

							Thanx, Paul

------------------------------------------------------------------------

rcu: hack to disable RCU idle checking

Not for inclusion -- for mainline the correct approach is to fix things
so that RCU is not invoked from CPUs that RCU believes to be idle.
Use the upcoming RCU_NONIDLE() macro for this, or the new tracing
functions designed for use from idle.

Not-signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>

diff --git a/kernel/rcutiny.c b/kernel/rcutiny.c
index 977296d..0829314 100644
--- a/kernel/rcutiny.c
+++ b/kernel/rcutiny.c
@@ -169,7 +169,7 @@ void rcu_irq_enter(void)
  */
 int rcu_is_cpu_idle(void)
 {
-	return !rcu_dynticks_nesting;
+	return false;
 }
 EXPORT_SYMBOL(rcu_is_cpu_idle);
 
diff --git a/kernel/rcutree.c b/kernel/rcutree.c
index 6c4a672..397cca8 100644
--- a/kernel/rcutree.c
+++ b/kernel/rcutree.c
@@ -572,12 +572,7 @@ void rcu_nmi_exit(void)
  */
 int rcu_is_cpu_idle(void)
 {
-	int ret;
-
-	preempt_disable();
-	ret = (atomic_read(&__get_cpu_var(rcu_dynticks).dynticks) & 0x1) == 0;
-	preempt_enable();
-	return ret;
+	return false;
 }
 EXPORT_SYMBOL(rcu_is_cpu_idle);
 


      reply	other threads:[~2012-03-09 15:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-05 13:54 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
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 [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=20120308212647.GV2348@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=Andre@jasper.es \
    --cc=a.p.zijlstra@chello.nl \
    --cc=eric.dumazet@gmail.com \
    --cc=fweisbec@gmail.com \
    --cc=jwboyer@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sergey.senozhatsky@gmail.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

Powered by JetHome