From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@elte.hu, laijs@cn.fujitsu.com, dipankar@in.ibm.com,
akpm@linux-foundation.org, mathieu.desnoyers@polymtl.ca,
josh@joshtriplett.org, niv@us.ibm.com, tglx@linutronix.de,
peterz@infradead.org, rostedt@goodmis.org,
Valdis.Kletnieks@vt.edu, dhowells@redhat.com,
eric.dumazet@gmail.com, darren@dvhart.com, fweisbec@gmail.com,
patches@linaro.org
Subject: [PATCH RFC idle] Make arm, sh, and x86 stop using RCU when idle
Date: Wed, 1 Feb 2012 16:42:53 -0800 [thread overview]
Message-ID: <20120202004253.GA10946@linux.vnet.ibm.com> (raw)
Hello!
RCU's shiny new diagnostics (thank you, Frederic!) for using RCU when idle
located a few problems in arm, sh, and x86. This patch series contains
alleged fixes for these problems. And they are real problems -- if RCU
believes that the CPU is idle, it is ignoring it. Which means that the
idle CPU can say "rcu_read_lock()" all it like, but there will be no
useful effect.
I was tempted to break these up, but doing so is bad for bisectability.
Thanx, Paul
------------------------------------------------------------------------
arch/arm/kernel/process.c | 2 --
arch/arm/mach-at91/cpuidle.c | 3 +++
arch/arm/mach-davinci/cpuidle.c | 3 +++
arch/arm/mach-exynos/common.c | 2 ++
arch/arm/mach-highbank/pm.c | 12 ++++++++++++
arch/arm/mach-imx/mm-imx3.c | 3 +++
arch/arm/mach-imx/pm-imx27.c | 4 ++++
arch/arm/mach-imx/pm-imx6q.c | 4 ++++
arch/arm/mach-kirkwood/cpuidle.c | 3 +++
arch/arm/mach-mx5/mm.c | 3 +++
arch/arm/mach-mx5/pm-imx5.c | 3 +++
arch/arm/mach-mxs/pm.c | 4 ++++
arch/arm/mach-omap1/pm.c | 4 ++++
arch/arm/mach-omap2/pm24xx.c | 2 ++
arch/arm/mach-omap2/pm34xx.c | 2 ++
arch/arm/mach-omap2/pm44xx.c | 3 +++
arch/arm/mach-pnx4008/pm.c | 2 ++
arch/arm/mach-prima2/pm.c | 4 ++++
arch/arm/mach-s5p64x0/common.c | 2 ++
arch/arm/mach-s5pc100/common.c | 2 ++
arch/arm/mach-s5pv210/common.c | 2 ++
arch/arm/mach-shmobile/cpuidle.c | 3 +++
arch/arm/mach-shmobile/pm-sh7372.c | 8 ++++++++
arch/sh/kernel/idle.c | 11 ++++++++---
arch/x86/kernel/process.c | 13 ++++++++++++-
arch/x86/kernel/process_32.c | 2 --
arch/x86/kernel/process_64.c | 4 ----
drivers/idle/intel_idle.c | 2 ++
28 files changed, 100 insertions(+), 12 deletions(-)
next reply other threads:[~2012-02-02 0:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 0:42 Paul E. McKenney [this message]
2012-02-02 0:43 ` [PATCH RFC idle 1/3] x86: Avoid invoking RCU when CPU is idle Paul E. McKenney
2012-02-02 0:43 ` [PATCH RFC idle 3/3] sh: " Paul E. McKenney
2012-02-02 1:54 ` [PATCH RFC idle 1/3] x86: " Frederic Weisbecker
2012-02-02 4:55 ` Paul E. McKenney
2012-02-02 0:48 ` [PATCH RFC idle] Make arm, sh, and x86 stop using RCU when idle Josh Triplett
2012-02-02 1:14 ` Paul E. McKenney
2012-02-02 2:29 ` Paul Mundt
2012-02-02 4:58 ` 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=20120202004253.GA10946@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=darren@dvhart.com \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=eric.dumazet@gmail.com \
--cc=fweisbec@gmail.com \
--cc=josh@joshtriplett.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mingo@elte.hu \
--cc=niv@us.ibm.com \
--cc=patches@linaro.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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).