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@efficios.com,
josh@joshtriplett.org, niv@us.ibm.com, tglx@linutronix.de,
peterz@infradead.org, rostedt@goodmis.org,
Valdis.Kletnieks@vt.edu, dhowells@redhat.com,
edumazet@google.com, darren@dvhart.com, fweisbec@gmail.com,
sbw@mit.edu, patches@linaro.org
Subject: [PATCH tip/core/urgent] no-CB CPU changes for 3.8
Date: Sat, 5 Jan 2013 08:58:17 -0800 [thread overview]
Message-ID: <20130105165817.GA13260@linux.vnet.ibm.com> (raw)
Hello!
This patch series contains a couple of fixes to the no-CBs CPU feature,
both courtesy of Paul Gortmaker:
1. Prevent soft-lockup complaints from no-CBs kthreads.
2. Make rcu_nocb_poll and early_param instead of a module parameter.
There is probably at least one more fix in this area.
Thanx, Paul
b/Documentation/kernel-parameters.txt | 2 +-
b/kernel/rcutree_plugin.h | 13 ++++++++++---
2 files changed, 11 insertions(+), 4 deletions(-)
next reply other threads:[~2013-01-05 16:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-05 16:58 Paul E. McKenney [this message]
2013-01-05 16:58 ` [PATCH tip/core/urgent 1/2] rcu: Prevent soft-lockup complaints about no-CBs CPUs Paul E. McKenney
2013-01-05 16:58 ` [PATCH tip/core/urgent 2/2] rcu: Make rcu_nocb_poll an early_param instead of module_param Paul E. McKenney
2013-01-05 17:21 ` [PATCH tip/core/urgent 1/2] rcu: Prevent soft-lockup complaints about no-CBs CPUs Frederic Weisbecker
2013-01-05 17:54 ` Paul E. McKenney
2013-01-05 18:29 ` Frederic Weisbecker
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=20130105165817.GA13260@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=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=josh@joshtriplett.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@elte.hu \
--cc=niv@us.ibm.com \
--cc=patches@linaro.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sbw@mit.edu \
--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