From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
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>,
"3.2.x.." <stable@kernel.org>
Subject: Re: [PATCH 01/10] alpha: Add missing RCU idle APIs on idle loop
Date: Wed, 22 Aug 2012 12:01:09 -0700 [thread overview]
Message-ID: <20120822190109.GH2447@linux.vnet.ibm.com> (raw)
In-Reply-To: <20120822173542.GD13674@somewhere>
On Wed, Aug 22, 2012 at 07:35:45PM +0200, Frederic Weisbecker wrote:
> On Wed, Aug 22, 2012 at 10:19:30AM -0700, Paul E. McKenney wrote:
> > On Wed, Aug 22, 2012 at 06:23:39PM +0200, 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.
> > >
> > > 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 Alpha's idle loop.
> > >
> > > Reported-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> > > Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
> > > Cc: Richard Henderson <rth@twiddle.net>
> > > Cc: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
> > > Cc: Matt Turner <mattst88@gmail.com>
> > > Cc: alpha <linux-alpha@vger.kernel.org>
> > > Cc: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> > > Cc: 3.2.x.. <stable@kernel.org>
> > > ---
> > > arch/alpha/kernel/process.c | 6 +++++-
> > > 1 files changed, 5 insertions(+), 1 deletions(-)
> > >
> > > diff --git a/arch/alpha/kernel/process.c b/arch/alpha/kernel/process.c
> > > index 153d3fc..2ebf7b5 100644
> > > --- a/arch/alpha/kernel/process.c
> > > +++ b/arch/alpha/kernel/process.c
> > > @@ -28,6 +28,7 @@
> > > #include <linux/tty.h>
> > > #include <linux/console.h>
> > > #include <linux/slab.h>
> > > +#include <linux/rcupdate.h>
> > >
> > > #include <asm/reg.h>
> > > #include <asm/uaccess.h>
> > > @@ -50,13 +51,16 @@ cpu_idle(void)
> > > {
> > > set_thread_flag(TIF_POLLING_NRFLAG);
> > >
> > > + preempt_disable();
> >
> > I don't understand the above preempt_disable() not having a matching
> > preempt_enable() at exit, but the rest of the patches in this series
> > look good to me.
>
> The current code is preemptable, at least it appears so because it calls
> schedule() directly. And if I call rcu_idle_enter() in a preemptable section,
> I'm in trouble because I'll schedule while in extended QS.
>
> Thus I need to disable preemption here at least until I call rcu_idle_exit().
>
> Now this is an endless loop so there is no need to re-enable
> preemption after the loop. And schedule_preempt_disabled()
> takes care of enabling preemption before schedule() and redisabling
> it afterward.
>
>
> >
> > Thanx, Paul
> >
> > > while (1) {
> > > /* FIXME -- EV6 and LCA45 know how to power down
> > > the CPU. */
> > >
> > > + rcu_idle_enter();
> > > while (!need_resched())
> > > cpu_relax();
> > > - schedule();
> > > + rcu_idle_exit();
> > > + schedule_preempt_disabled();
> > > }
Understood, but what I don't understand is why you don't need a
preempt_enable() right here.
Thanx, Paul
> > > }
> > >
> > > --
> > > 1.7.5.4
> > >
> >
>
next prev parent reply other threads:[~2012-08-22 19:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 16:23 [PATCH 00/10] rcu: Add missing RCU idle APIs on idle loop 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 [this message]
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
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=20120822190109.GH2447@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=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=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;
as well as URLs for NNTP newsgroup(s).