public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.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: Sun, 4 Sep 2011 23:05:07 +0200	[thread overview]
Message-ID: <20110904210504.GC5587@somewhere> (raw)
In-Reply-To: <20110904210130.GL2411@linux.vnet.ibm.com>

On Sun, Sep 04, 2011 at 02:01:30PM -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.
> 
> Hello, Frederic,
> 
> Some of my testing indicates that it is necessary to push
> tick_nohz_enter_idle() and tick_nohz_exit_idle() further down in the
> powerpc case due to tracing that happens in functions called from
> ppc_md.power_save().  My current guess is that for the pSeries flavor
> of powerpc, these must be called from __trace_hcall_entry() and
> __trace_hcall_exit(), probably controlled by a powerpc-specific per-CPU
> variable.
> 
> The following functions likely need help.
> 
> 	cbe_power_save()
> 	cpm_idle()
> 	e500_idle()
> 	idle_doze()
> 	idle_spin()
> 	ppc44x_idle()
> 	ppc6xx_idle()
> 	ps3_power_save()
> 	pseries_dedicated_idle_sleep()
> 	pseries_shared_idle_sleep()
> 
> I am continuing testing.  In the meantime, other thoughts?
> 
> 							Thanx, Paul

Yeah sure, I still have that in my todo list. I wanted to ensure
first that at least you are fine with the new interface before I go
fixing more detected bad callsites.

Thanks.

  reply	other threads:[~2011-09-04 21:05 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 [this message]
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
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=20110904210504.GC5587@somewhere \
    --to=fweisbec@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=cmetcalf@tilera.com \
    --cc=davem@davemloft.net \
    --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=paulmck@linux.vnet.ibm.com \
    --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