From: Philipp Schrader <philipp@peloton-tech.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-rt-users@vger.kernel.org
Subject: Re: RCU splat on boot from an idle CPU
Date: Thu, 3 Sep 2015 09:55:46 -0700 [thread overview]
Message-ID: <20150903165411.GA25462@philipp-debian.peloton-tech.com> (raw)
In-Reply-To: <20150902230729.GZ4029@linux.vnet.ibm.com>
On Wed, Sep 02, 2015 at 04:07:29PM -0700, Paul E. McKenney wrote:
> On Wed, Sep 02, 2015 at 03:10:04PM -0700, Philipp Schrader wrote:
> > I've got the following patch now that makes the splat disappear:
> >
> > diff --git a/kernel/trace/trace_irqsoff.c b/kernel/trace/trace_irqsoff.c
> > index aaade2e..d0e1d0e 100644
> > --- a/kernel/trace/trace_irqsoff.c
> > +++ b/kernel/trace/trace_irqsoff.c
> > @@ -450,7 +450,7 @@ EXPORT_SYMBOL_GPL(stop_critical_timings);
> > #ifdef CONFIG_PROVE_LOCKING
> > void time_hardirqs_on(unsigned long a0, unsigned long a1)
> > {
> > - trace_preemptirqsoff_hist(IRQS_ON, 0);
> > + trace_preemptirqsoff_hist_rcuidle(IRQS_ON, 0);
> > if (!preempt_trace() && irq_trace())
> > stop_critical_timing(a0, a1);
> > }
> > @@ -459,7 +459,7 @@ void time_hardirqs_off(unsigned long a0, unsigned long a1)
> > {
> > if (!preempt_trace() && irq_trace())
> > start_critical_timing(a0, a1);
> > - trace_preemptirqsoff_hist(IRQS_OFF, 1);
> > + trace_preemptirqsoff_hist_rcuidle(IRQS_OFF, 1);
> > }
> >
> > #else /* !CONFIG_PROVE_LOCKING */
> >
> > Does that look reasonable?
> > Or could this cause a problem down the road?
>
> Looks good to me!
Should I submit a patch for this or is this just a fix for my particular kernel
configuration? I don't yet understand the code well enough to know the answer.
Thanks,
Philipp
next prev parent reply other threads:[~2015-09-03 16:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 0:46 RCU splat on boot from an idle CPU Philipp Schrader
2015-09-01 15:35 ` Thomas Gleixner
2015-09-02 19:38 ` Steven Rostedt
2015-09-02 22:10 ` Philipp Schrader
2015-09-02 23:07 ` Paul E. McKenney
2015-09-03 16:53 ` Steven Rostedt
2015-09-03 21:39 ` Paul E. McKenney
2015-09-03 16:55 ` Philipp Schrader [this message]
2015-09-03 17:12 ` Steven Rostedt
2015-12-11 16:32 ` Sebastian Andrzej Siewior
2015-12-11 16:46 ` Philipp Schrader
2015-12-11 16:53 ` Paul E. McKenney
2015-12-11 16:59 ` Philipp Schrader
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=20150903165411.GA25462@philipp-debian.peloton-tech.com \
--to=philipp@peloton-tech.com \
--cc=linux-rt-users@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).