linux-parisc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <gregkh@linuxfoundation.org>
To: fweisbec@gmail.com, deller@gmx.de, gregkh@linuxfoundation.org,
	jejb@parisc-linux.org, josh@joshtriplett.org,
	linux-parisc@vger.kernel.org, paulmck@linux.vnet.ibm.com
Cc: <stable@vger.kernel.org>, <stable-commits@vger.kernel.org>
Subject: Patch "parisc: Add missing RCU idle APIs on idle loop" has been added to the 3.4-stable tree
Date: Wed, 10 Oct 2012 09:25:05 +0900	[thread overview]
Message-ID: <13498287052440@kroah.org> (raw)


This is a note to let you know that I've just added the patch titled

    parisc: Add missing RCU idle APIs on idle loop

to the 3.4-stable tree which can be found at:
    http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
     parisc-add-missing-rcu-idle-apis-on-idle-loop.patch
and it can be found in the queue-3.4 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@vger.kernel.org> know about it.


>From fbe752188d5589e7fcbb8e79824e560f77dccc92 Mon Sep 17 00:00:00 2001
From: Frederic Weisbecker <fweisbec@gmail.com>
Date: Wed, 22 Aug 2012 17:27:34 +0200
Subject: parisc: Add missing RCU idle APIs on idle loop

From: Frederic Weisbecker <fweisbec@gmail.com>

commit fbe752188d5589e7fcbb8e79824e560f77dccc92 upstream.

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.

So nowadays, rcu_idle_enter() and rcu_idle_exit() must
be called by the architecture to tell RCU about the part
in the idle loop that doesn't make use of rcu read side
critical sections, typically the part that puts the CPU
in low power mode.

This is necessary for RCU to find the quiescent states in
idle in order to complete grace periods.

Add this missing pair of calls in the parisc's idle loop.

Reported-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
Cc: James E.J. Bottomley <jejb@parisc-linux.org>
Cc: Helge Deller <deller@gmx.de>
Cc: Parisc <linux-parisc@vger.kernel.org>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Reviewed-by: Josh Triplett <josh@joshtriplett.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

---
 arch/parisc/kernel/process.c |    3 +++
 1 file changed, 3 insertions(+)

--- a/arch/parisc/kernel/process.c
+++ b/arch/parisc/kernel/process.c
@@ -48,6 +48,7 @@
 #include <linux/unistd.h>
 #include <linux/kallsyms.h>
 #include <linux/uaccess.h>
+#include <linux/rcupdate.h>
 
 #include <asm/io.h>
 #include <asm/asm-offsets.h>
@@ -69,8 +70,10 @@ void cpu_idle(void)
 
 	/* endless idle loop with no priority at all */
 	while (1) {
+		rcu_idle_enter();
 		while (!need_resched())
 			barrier();
+		rcu_idle_exit();
 		schedule_preempt_disabled();
 		check_pgt_cache();
 	}


Patches currently in stable-queue which might be from fweisbec@gmail.com are

queue-3.4/frv-add-missing-rcu-idle-apis-on-idle-loop.patch
queue-3.4/cris-add-missing-rcu-idle-apis-on-idle-loop.patch
queue-3.4/m68k-add-missing-rcu-idle-apis-on-idle-loop.patch
queue-3.4/alpha-add-missing-rcu-idle-apis-on-idle-loop.patch
queue-3.4/h8300-add-missing-rcu-idle-apis-on-idle-loop.patch
queue-3.4/parisc-add-missing-rcu-idle-apis-on-idle-loop.patch
queue-3.4/m32r-add-missing-rcu-idle-apis-on-idle-loop.patch
queue-3.4/score-add-missing-rcu-idle-apis-on-idle-loop.patch
queue-3.4/mn10300-add-missing-rcu-idle-apis-on-idle-loop.patch
queue-3.4/xtensa-add-missing-rcu-idle-apis-on-idle-loop.patch

                 reply	other threads:[~2012-10-10  0:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=13498287052440@kroah.org \
    --to=gregkh@linuxfoundation.org \
    --cc=deller@gmx.de \
    --cc=fweisbec@gmail.com \
    --cc=jejb@parisc-linux.org \
    --cc=josh@joshtriplett.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).