From: Frederic Weisbecker <fweisbec@gmail.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
"Paul E . McKenney" <paulmck@linux.vnet.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Steven Rostedt <rostedt@goodmis.org>
Subject: [PATCH 0/2 v2] rcu: Fix series of spurious RCU softirqs
Date: Fri, 10 Dec 2010 22:11:09 +0100 [thread overview]
Message-ID: <1292015471-19227-1-git-send-email-fweisbec@gmail.com> (raw)
Hi,
Following Lai's idea.
An example of such series of spurious softirqs:
http://tglx.de/~fweisbec/trace_rcu_softirq.txt
In that example, the rcu softirq is raised at every tick
during 20 secs (was perhaps more, but the trace snapshot happened
during 20 secs). It happens randomly.
Ah and it survived several hours of rcutorture (with rcu cpu stall
detection).
Thanks.
Frederic Weisbecker (2):
rcu: Stop chasing QS if another CPU did it for us
rcu: Keep gpnum and completed fields synchronized
kernel/rcutree.c | 17 +++++++++++++++++
1 files changed, 17 insertions(+), 0 deletions(-)
--
1.7.3.2
next reply other threads:[~2010-12-10 21:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 21:11 Frederic Weisbecker [this message]
2010-12-10 21:11 ` [PATCH 1/2] rcu: Stop chasing QS if another CPU did it for us Frederic Weisbecker
2010-12-10 22:58 ` Paul E. McKenney
2010-12-10 23:33 ` Frederic Weisbecker
2010-12-10 21:14 ` [PATCH 0/2 v2] rcu: Fix series of spurious RCU softirqs Frederic Weisbecker
[not found] ` <1292015471-19227-3-git-send-email-fweisbec@gmail.com>
2010-12-10 23:02 ` [PATCH 2/2] rcu: Keep gpnum and completed fields synchronized Paul E. McKenney
2010-12-10 23:39 ` Paul E. McKenney
2010-12-10 23:47 ` Frederic Weisbecker
2010-12-11 0:04 ` Paul E. McKenney
2010-12-11 0:15 ` Frederic Weisbecker
2010-12-11 0:58 ` Paul E. McKenney
2010-12-11 1:21 ` Frederic Weisbecker
2010-12-11 6:36 ` Paul E. McKenney
2010-12-11 0:00 ` Frederic Weisbecker
2010-12-11 0:48 ` Paul E. McKenney
2010-12-11 0:51 ` 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=1292015471-19227-1-git-send-email-fweisbec@gmail.com \
--to=fweisbec@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--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).