mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Michael Cree <mcree@orcon.net.nz>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Richard Henderson <rth@twiddle.net>,
	Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
	Matt Turner <mattst88@gmail.com>,
	alpha <linux-alpha@vger.kernel.org>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	"3.2.x.." <stable@kernel.org>
Subject: Re: [PATCH 01/10] alpha: Add missing RCU idle APIs on idle loop
Date: Thu, 23 Aug 2012 12:58:19 +0200	[thread overview]
Message-ID: <20120823105816.GB18835@somewhere.redhat.com> (raw)
In-Reply-To: <5035F8A2.1070702@orcon.net.nz>

On Thu, Aug 23, 2012 at 09:32:18PM +1200, Michael Cree wrote:
> On 23/08/12 04:23, Frederic Weisbecker wrote:
> > In the old times, the whole idle task was considered
> > as an RCU quiescent state. But as RCU became more and
> > more successful overtime, some RCU read side critical
> > section have been added even in the code of some
> > architectures idle tasks, for tracing for example.
> 
> Fantastic!  It fixes RCU CPU stalls that we were seeing on the SMP
> kernel when built for generic Alpha.
> 
> A build of glibc and running its test suite reliably triggers RCU CPU
> stalls when running a kernel built for generic Alpha.  I have just built
> glibc and ran its test suite twice with no RCU CPU stalls with this
> patch against a 3.5.2 kernel!  Nice.  Very nice.
> 
> I see the stable queue is CCed but I note the patch does not apply
> cleanly to the 3.2.y kernel.  It would be nice to have a backport of the
> patches for the 3.2 stable kernel.

Sure.

> 
> So feel free to add:
> 
> Tested-by:  Michael Cree <mcree@orcon.net.nz>

Thanks, but I need to refactor the patch, I suspect a problem with CONFIG_PREEMPT.

  reply	other threads:[~2012-08-23 10:58 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-22 16:23 [PATCH 00/10] rcu: " Frederic Weisbecker
2012-08-22 16:23 ` [PATCH 01/10] alpha: " Frederic Weisbecker
2012-08-22 17:19   ` Paul E. McKenney
2012-08-22 17:35     ` Frederic Weisbecker
2012-08-22 19:01       ` Paul E. McKenney
2012-08-23 10:42         ` Frederic Weisbecker
2012-08-23 12:25           ` Paul E. McKenney
2012-08-23  9:32   ` Michael Cree
2012-08-23 10:58     ` Frederic Weisbecker [this message]
2012-08-22 16:23 ` [PATCH 02/10] cris: " Frederic Weisbecker
2012-08-22 16:23 ` [PATCH 03/10] frv: " Frederic Weisbecker
2012-08-22 16:23 ` [PATCH 04/10] h8300: " Frederic Weisbecker
2012-08-22 16:23 ` [PATCH 05/10] m32r: " Frederic Weisbecker
2012-08-22 16:23 ` [PATCH 06/10] m68k: " Frederic Weisbecker
2012-08-22 16:23 ` [PATCH 07/10] mn10300: " Frederic Weisbecker
2012-08-22 16:23 ` [PATCH 08/10] parisc: " Frederic Weisbecker
2012-08-24 13:26   ` John David Anglin
2012-08-22 16:23 ` [PATCH 09/10] score: " Frederic Weisbecker
2012-08-22 16:23 ` [PATCH 10/10] xtensa: " Frederic Weisbecker
2012-08-22 17:18 ` [PATCH 00/10] rcu: " Geert Uytterhoeven
2012-08-23 11:02   ` Frederic Weisbecker
2012-08-23 20:23     ` Geert Uytterhoeven
2012-08-23 21:50       ` Frederic Weisbecker
2012-09-17 20:31         ` Geert Uytterhoeven
2012-09-17 20:55           ` 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=20120823105816.GB18835@somewhere.redhat.com \
    --to=fweisbec@gmail.com \
    --cc=ink@jurassic.park.msu.ru \
    --cc=linux-alpha@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mattst88@gmail.com \
    --cc=mcree@orcon.net.nz \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=rth@twiddle.net \
    --cc=stable@kernel.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