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>,
Josh Triplett <josh@joshtriplett.org>
Subject: [PATCH 2/4] rcu: Irq nesting is always 0 on rcu_enter_idle_common
Date: Mon, 28 Nov 2011 22:24:45 +0100 [thread overview]
Message-ID: <1322515487-18690-3-git-send-email-fweisbec@gmail.com> (raw)
In-Reply-To: <1322515487-18690-1-git-send-email-fweisbec@gmail.com>
So pass 0 directly as a nesting value on the tracing calls.
Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Josh Triplett <josh@joshtriplett.org>
---
kernel/rcutree.c | 5 ++---
1 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/kernel/rcutree.c b/kernel/rcutree.c
index c2aaadf..b80cb41 100644
--- a/kernel/rcutree.c
+++ b/kernel/rcutree.c
@@ -350,11 +350,10 @@ static int rcu_implicit_offline_qs(struct rcu_data *rdp)
*/
static void rcu_idle_enter_common(struct rcu_dynticks *rdtp)
{
- trace_rcu_dyntick("Start", rdtp->dynticks_nesting);
+ trace_rcu_dyntick("Start", 0);
if (!idle_cpu(smp_processor_id())) {
WARN_ON_ONCE(1); /* must be idle task! */
- trace_rcu_dyntick("Error on entry: not idle task",
- rdtp->dynticks_nesting);
+ trace_rcu_dyntick("Error on entry: not idle task", 0);
ftrace_dump(DUMP_ALL);
}
/* CPUs seeing atomic_inc() must see prior RCU read-side crit sects */
--
1.7.5.4
next prev parent reply other threads:[~2011-11-28 21:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 21:24 [PATCH 0/4] rcu: Make new RCU dynticks API work with nohz cpusets Frederic Weisbecker
2011-11-28 21:24 ` [PATCH 1/4] rcu: Don't check irq nesting from rcu idle entry/exit Frederic Weisbecker
2011-11-29 0:22 ` Paul E. McKenney
2011-11-29 0:26 ` Frederic Weisbecker
2011-11-29 0:39 ` Paul E. McKenney
2011-11-29 0:58 ` Frederic Weisbecker
2011-11-28 21:24 ` Frederic Weisbecker [this message]
2011-11-29 0:29 ` [PATCH 2/4] rcu: Irq nesting is always 0 on rcu_enter_idle_common Paul E. McKenney
2011-11-29 1:00 ` Frederic Weisbecker
2011-11-28 21:24 ` [PATCH 3/4 RFC] rcu: New rcu_user_enter() and rcu_user_exit() APIs Frederic Weisbecker
2011-11-28 21:24 ` [PATCH 4/4 RFC] rcu: New rcu_user_enter_irq() and rcu_user_exit_irq() APIs Frederic Weisbecker
2011-11-28 21:53 ` Josh Triplett
2011-11-29 1:00 ` Paul E. McKenney
2011-11-29 5:21 ` Josh Triplett
2011-11-29 14:05 ` Frederic Weisbecker
2011-11-29 18:23 ` Paul E. McKenney
2011-11-29 13:53 ` Frederic Weisbecker
2011-11-29 5:22 ` [PATCH 0/4] rcu: Make new RCU dynticks API work with nohz cpusets Josh Triplett
2011-11-29 5:43 ` Paul E. McKenney
2011-11-29 8:48 ` Josh Triplett
2011-11-29 17:44 ` Paul E. McKenney
2011-11-29 18:07 ` 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=1322515487-18690-3-git-send-email-fweisbec@gmail.com \
--to=fweisbec@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®