All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: mingo@elte.hu
Cc: paul.gortmaker@windriver.com, fweisbec@gmail.com,
	linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Subject: [GIT PULL rcu/urgent] Fixes for RCU regressions in 3.8
Date: Fri, 11 Jan 2013 08:08:13 -0800	[thread overview]
Message-ID: <20130111160813.GA14503@linux.vnet.ibm.com> (raw)

Hello, Ingo,

Paul Gortmaker found some problems with no-CBs-CPU support in 3.8
mainline, and kindly supplied fixes.  The first problem is soft-lockup
complaints that can occur on systems running with no-CBs CPUs that have
long periods of time where RCU is completely idle, which can happen on
some embedded systems.  The second problem is a documentation error
for the "rcutree.rcu_nocb_poll" boot parameter.  In this case, Paul Gortmaker
(rightly) noted that the need for "rcutree." was inconsistent with the
"rcu_nocbs=<cpumap>" boot parameter.  The fix therefore to make the boot
parameter named "rcu_nocb_poll".

These problems only affect kernels built with the new CONFIG_RCU_NOCB_CPU
kernel parameter, but still should be fixed.

These fixes are available in the git repository at:
  git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/urgent

							Thanx, Paul

------------------>
Paul Gortmaker (2):
      rcu: Prevent soft-lockup complaints about no-CBs CPUs
      rcu: Make rcu_nocb_poll an early_param instead of module_param

 Documentation/kernel-parameters.txt |    2 +-
 kernel/rcutree_plugin.h             |   13 ++++++++++---
 2 files changed, 11 insertions(+), 4 deletions(-)

             reply	other threads:[~2013-01-11 16:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-11 16:08 Paul E. McKenney [this message]
2013-01-24 12:28 ` [GIT PULL rcu/urgent] Fixes for RCU regressions in 3.8 Ingo Molnar

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=20130111160813.GA14503@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paul.gortmaker@windriver.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.