From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
David Miller <davem@davemloft.net>,
Chris Metcalf <cmetcalf@tilera.com>,
Guan Xuetao <gxt@mprc.pku.edu.cn>,
Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>,
Mike Frysinger <vapier@gentoo.org>,
Ralf Baechle <ralf@linux-mips.org>, Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Russell King <linux@arm.linux.org.uk>,
Paul Mackerras <paulus@samba.org>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Paul Mundt <lethal@linux-sh.org>
Subject: Re: [PATCH 1/4] nohz: Split extended quiescent state handling from nohz switch
Date: Tue, 13 Sep 2011 09:49:33 -0700 [thread overview]
Message-ID: <20110913164933.GF2416@linux.vnet.ibm.com> (raw)
In-Reply-To: <20110913000637.GA17335@somewhere.redhat.com>
On Tue, Sep 13, 2011 at 02:06:45AM +0200, Frederic Weisbecker wrote:
> On Wed, Sep 07, 2011 at 07:22:33AM -0700, Paul E. McKenney wrote:
> > On Sun, Sep 04, 2011 at 04:36:43PM -0700, Paul E. McKenney wrote:
> > > On Sat, Aug 20, 2011 at 07:30:49PM +0200, Frederic Weisbecker wrote:
> > > > It is assumed that rcu won't be used once we switch to tickless
> > > > mode and until we restart the tick. However this is not always
> > > > true, as in x86-64 where we dereference the idle notifiers after
> > > > the tick is stopped.
> > > >
> > > > To prepare for fixing this, split the tickless mode switching and
> > > > RCU extended quiescent state logics.
> > > > Make tick_nohz_stop/restart_sched_tick() RCU agnostic but provide
> > > > a new pair of APIs tick_nohz_enter/exit_idle() that keep the
> > > > old behaviour by handling both the nohz mode and RCU extended
> > > > quiescent states, then convert every archs to use these.
> > > >
> > > > Archs that want to switch to RCU extended QS to some custom points
> > > > can do it later by changing the parameter in tick_nohz_enter,exit_idle()
> > > > to false and call rcu_enter,exit() separately.
> > >
> > > This approach looks quite good to me! A few comments below.
> >
> > But I get RCU stall warnings when running it on powerpc on top of
> > the patch set at:
> >
> > https://lkml.org/lkml/2011/9/7/64
> >
> > At first glance, it appears that CPUs are entering dyntick-idle
> > mode without RCU being informed. Any thoughts on diagnostics?
> >
> > Thanx, Paul
>
> I've just tested with your rcu/next branch from github and applied
> my patches on top of it but did not experience a stall in x86.
Thank you for checking this!
> That may be related to powerpc more precisely, or may be any arch
> but on some particular condition.
OK, I guess my next step is to put a WARN_ON_ONCE() in the idle loop
to check to see if there might be some other idle loop buried in
PowerPC somewhere...
Thanx, Paul
next prev parent reply other threads:[~2011-09-13 16:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-20 17:30 [PATCH 0/4 v2] rcu: Fix some rcu uses in extended quiescent state Frederic Weisbecker
2011-08-20 17:30 ` [PATCH 1/4] nohz: Split extended quiescent state handling from nohz switch Frederic Weisbecker
2011-08-20 17:39 ` Mike Frysinger
2011-08-22 2:02 ` Guan Xuetao
2011-09-04 21:01 ` Paul E. McKenney
2011-09-04 21:05 ` Frederic Weisbecker
2011-09-04 23:36 ` Paul E. McKenney
2011-09-06 14:58 ` Frederic Weisbecker
2011-09-07 14:22 ` Paul E. McKenney
2011-09-07 21:39 ` Frederic Weisbecker
2011-09-13 0:06 ` Frederic Weisbecker
2011-09-13 16:49 ` Paul E. McKenney [this message]
2011-08-20 17:30 ` [PATCH 2/4] x86: Enter rcu extended qs after idle notifier call Frederic Weisbecker
2011-08-20 17:30 ` [PATCH 3/4] x86: Call idle notifier after irq_enter() Frederic Weisbecker
2011-08-20 17:30 ` [PATCH 4/4] rcu: Fix early call to rcu_irq_exit() Frederic Weisbecker
2011-09-04 23:38 ` 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=20110913164933.GF2416@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=cmetcalf@tilera.com \
--cc=davem@davemloft.net \
--cc=fweisbec@gmail.com \
--cc=gxt@mprc.pku.edu.cn \
--cc=hans-christian.egtvedt@atmel.com \
--cc=heiko.carstens@de.ibm.com \
--cc=hpa@zytor.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=ralf@linux-mips.org \
--cc=tglx@linutronix.de \
--cc=vapier@gentoo.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