From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: tglx@linutronix.de, jkacur@redhat.com
Subject: [PATCH RFC] rcu: RCU CPU stall patches backported to 2.6.33-rc8
Date: Mon, 22 Feb 2010 17:46:54 -0800 [thread overview]
Message-ID: <20100223014654.GA3404@linux.vnet.ibm.com> (raw)
Hello!
This set backports a couple of RCU CPU stall detection patches from the
earlier series (http://lkml.org/lkml/2010/2/22/384) to 2.6.33-rc8 to
help track down some NMI issues.
These two patches fix an embarrassing deadlock that can affect
TREE_PREEMPT_RCU and add additional per-task output when tasks stall the
RCU grace period.
b/kernel/rcutree.c | 2 +
b/kernel/rcutree.h | 1
b/kernel/rcutree_plugin.h | 4 ---
b/lib/Kconfig.debug | 13 ++++++++++-
kernel/rcutree.c | 4 +++
kernel/rcutree_plugin.h | 52 ++++++++++++++++++++++++++++++++++++++++++++++
6 files changed, 71 insertions(+), 5 deletions(-)
next reply other threads:[~2010-02-23 1:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 1:46 Paul E. McKenney [this message]
2010-02-23 1:47 ` [PATCH RFC 1/2] rcu: fix deadlock in TREE_PREEMPT_RCU CPU stall detection Paul E. McKenney
2010-02-23 1:47 ` [PATCH RFC 2/2] rcu: add RCU_CPU_STALL_VERBOSE to dump detailed per-task information 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=20100223014654.GA3404@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.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