From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: Rojhalat Ibrahim <imr@rtschenk.de>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: Regression in RCU subsystem in latest mainline kernel
Date: Tue, 25 Jun 2013 17:36:25 +1000 [thread overview]
Message-ID: <1372145785.3944.195.camel@pasglop> (raw)
In-Reply-To: <20130625071914.GA29957@concordia>
On Tue, 2013-06-25 at 17:19 +1000, Michael Ellerman wrote:
> Here's another trace from 3.10-rc7 plus a few local patches.
>
> We suspect that the perf enable could be causing a flood of
> interrupts, but why
> that's clogging things up so badly who knows.
Additionally, perf being potentially NMIs , we might be hitting a bad
case of reentrance in RCU ... hard to tell.
Cheers,
Ben.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Steven Rostedt <rostedt@goodmis.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Rojhalat Ibrahim <imr@rtschenk.de>,
linux-kernel@vger.kernel.org
Subject: Re: Regression in RCU subsystem in latest mainline kernel
Date: Tue, 25 Jun 2013 17:36:25 +1000 [thread overview]
Message-ID: <1372145785.3944.195.camel@pasglop> (raw)
In-Reply-To: <20130625071914.GA29957@concordia>
On Tue, 2013-06-25 at 17:19 +1000, Michael Ellerman wrote:
> Here's another trace from 3.10-rc7 plus a few local patches.
>
> We suspect that the perf enable could be causing a flood of
> interrupts, but why
> that's clogging things up so badly who knows.
Additionally, perf being potentially NMIs , we might be hitting a bad
case of reentrance in RCU ... hard to tell.
Cheers,
Ben.
next prev parent reply other threads:[~2013-06-25 7:37 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 11:47 Regression in RCU subsystem in latest mainline kernel Rojhalat Ibrahim
2013-06-14 12:28 ` Paul E. McKenney
2013-06-14 12:46 ` Rojhalat Ibrahim
2013-06-14 21:06 ` Steven Rostedt
2013-06-14 21:06 ` Steven Rostedt
2013-06-15 2:02 ` Benjamin Herrenschmidt
2013-06-15 2:02 ` Benjamin Herrenschmidt
2013-06-15 2:17 ` Steven Rostedt
2013-06-15 2:17 ` Steven Rostedt
2013-06-15 2:21 ` Benjamin Herrenschmidt
2013-06-15 2:21 ` Benjamin Herrenschmidt
2013-06-15 2:31 ` Steven Rostedt
2013-06-15 2:31 ` Steven Rostedt
2013-06-15 2:51 ` Paul E. McKenney
2013-06-15 2:51 ` Paul E. McKenney
2013-06-17 13:21 ` Rojhalat Ibrahim
2013-06-17 13:21 ` Rojhalat Ibrahim
2013-06-17 13:51 ` Steven Rostedt
2013-06-17 13:51 ` Steven Rostedt
2013-06-17 7:42 ` Michael Ellerman
2013-06-17 7:42 ` Michael Ellerman
2013-06-19 4:09 ` Paul E. McKenney
2013-06-19 4:09 ` Paul E. McKenney
2013-06-25 7:19 ` Michael Ellerman
2013-06-25 7:19 ` Michael Ellerman
2013-06-25 7:36 ` Benjamin Herrenschmidt [this message]
2013-06-25 7:36 ` Benjamin Herrenschmidt
2013-06-25 7:44 ` Michael Ellerman
2013-06-25 7:44 ` Michael Ellerman
2013-06-25 16:03 ` Paul E. McKenney
2013-06-25 16:03 ` Paul E. McKenney
2013-06-26 8:10 ` Michael Ellerman
2013-06-26 8:10 ` Michael Ellerman
2013-06-26 14:16 ` Paul E. McKenney
2013-06-26 14:16 ` 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=1372145785.3944.195.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=imr@rtschenk.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=michael@ellerman.id.au \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
/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.