linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
	m68k <linux-m68k@vger.kernel.org>,
	"3.2.x.." <stable@vger.kernel.org>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: [PATCH 07/11] m68k: Add missing RCU idle APIs on idle loop
Date: Thu, 23 Aug 2012 16:58:31 +0200	[thread overview]
Message-ID: <1345733915-20040-8-git-send-email-fweisbec@gmail.com> (raw)
In-Reply-To: <1345733915-20040-1-git-send-email-fweisbec@gmail.com>

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 m68k's idle loop.

Reported-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: m68k <linux-m68k@lists.linux-m68k.org>
Cc: 3.2.x.. <stable@vger.kernel.org>
Cc: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
---
 arch/m68k/kernel/process.c |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/arch/m68k/kernel/process.c b/arch/m68k/kernel/process.c
index c488e3c..ac2892e 100644
--- a/arch/m68k/kernel/process.c
+++ b/arch/m68k/kernel/process.c
@@ -25,6 +25,7 @@
 #include <linux/reboot.h>
 #include <linux/init_task.h>
 #include <linux/mqueue.h>
+#include <linux/rcupdate.h>
 
 #include <asm/uaccess.h>
 #include <asm/traps.h>
@@ -75,8 +76,10 @@ void cpu_idle(void)
 {
 	/* endless idle loop with no priority at all */
 	while (1) {
+		rcu_idle_enter();
 		while (!need_resched())
 			idle();
+		rcu_idle_exit();
 		schedule_preempt_disabled();
 	}
 }
-- 
1.7.5.4


  parent reply	other threads:[~2012-08-23 15:00 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-23 14:58 [PATCH 00/11] rcu: Add missing RCU idle APIs on idle loop v2 Frederic Weisbecker
2012-08-23 14:58 ` [PATCH 01/11] alpha: Fix preemption handling in idle loop Frederic Weisbecker
2012-08-23 14:58 ` [PATCH 02/11] alpha: Add missing RCU idle APIs on " Frederic Weisbecker
2012-08-23 14:58 ` [PATCH 03/11] cris: " Frederic Weisbecker
2012-08-23 14:58 ` [PATCH 04/11] frv: " Frederic Weisbecker
2012-08-23 14:58 ` [PATCH 05/11] h8300: " Frederic Weisbecker
2012-08-23 14:58 ` [PATCH 06/11] m32r: " Frederic Weisbecker
2012-08-23 14:58 ` Frederic Weisbecker [this message]
2012-08-23 14:58 ` [PATCH 08/11] mn10300: " Frederic Weisbecker
2012-08-23 14:58 ` [PATCH 09/11] parisc: " Frederic Weisbecker
2012-08-23 14:58 ` [PATCH 10/11] score: " Frederic Weisbecker
2012-08-23 14:58 ` [PATCH 11/11] xtensa: " Frederic Weisbecker
2012-08-24 21:26 ` [PATCH 00/11] rcu: Add missing RCU idle APIs on idle loop v2 Paul E. McKenney
2012-08-25  1:19   ` Ben Hutchings
2012-08-25  2:10     ` Michael Cree
2012-08-25  3:50     ` Paul E. McKenney
2012-08-25 13:16       ` Frederic Weisbecker
2012-08-25 16:18         ` Paul E. McKenney
2012-08-25 21:15           ` Michael Cree
2012-08-26  0:12             ` Paul E. McKenney
2012-08-26  9:21               ` Tobias Klausmann
2012-09-10 21:53                 ` Frederic Weisbecker
2012-09-12 18:01                   ` Tobias Klausmann
2012-09-10 21:56     ` Frederic Weisbecker
2012-09-10 22:58       ` Paul E. McKenney
2012-09-11 12:35         ` Frederic Weisbecker

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=1345733915-20040-8-git-send-email-fweisbec@gmail.com \
    --to=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --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).