From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] rcu: Hotplug and PROVE_RCU_DELAY not playing well together
Date: Tue, 4 Jun 2013 06:14:08 -0700 [thread overview]
Message-ID: <20130604131408.GK11597@linux.vnet.ibm.com> (raw)
In-Reply-To: <1370283591.26799.95.camel@gandalf.local.home>
On Mon, Jun 03, 2013 at 02:19:51PM -0400, Steven Rostedt wrote:
> On Sun, 2013-06-02 at 07:18 -0700, Paul E. McKenney wrote:
>
> > ------------------------------------------------------------------------
> >
> > diff --git a/kernel/rcutree.c b/kernel/rcutree.c
> > index d12470e..9a08bdc 100644
> > --- a/kernel/rcutree.c
> > +++ b/kernel/rcutree.c
> > @@ -1320,9 +1320,9 @@ static int rcu_gp_init(struct rcu_state *rsp)
> > rnp->grphi, rnp->qsmask);
> > raw_spin_unlock_irq(&rnp->lock);
> > #ifdef CONFIG_PROVE_RCU_DELAY
> > - if ((prandom_u32() % (rcu_num_nodes * 8)) == 0 &&
> > + if ((prandom_u32() % (rcu_num_nodes + 1)) == 0 &&
> > system_state == SYSTEM_RUNNING)
> > - schedule_timeout_uninterruptible(2);
> > + udelay(200);
> > #endif /* #ifdef CONFIG_PROVE_RCU_DELAY */
> > cond_resched();
> > }
>
> I ran this for a bit. Where it usually crashes in less than a minute,
> this ran for over 10 minutes without issue.
>
> Tested-by: Steven Rostedt <rostedt@goodmis.org>
Thank you!!!
And yes, if this was production code rather than test code, I probably
would have favored a solution like yours.
Thanx, Paul
prev parent reply other threads:[~2013-06-05 2:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 21:27 [RFC][PATCH] rcu: Hotplug and PROVE_RCU_DELAY not playing well together Steven Rostedt
2013-06-02 2:54 ` Paul E. McKenney
2013-06-02 14:18 ` Paul E. McKenney
2013-06-03 15:32 ` Steven Rostedt
2013-06-03 18:19 ` Steven Rostedt
2013-06-04 13:14 ` Paul E. McKenney [this message]
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=20130604131408.GK11597@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--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 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.