From: Will Deacon <will.deacon@arm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Drew Richardson <Drew.Richardson@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Arnaldo <acme@redhat.com>, Pawel Moll <Pawel.Moll@arm.com>,
Wade Cherry <Wade.Cherry@arm.com>
Subject: Re: Perf Oops on 3.14-rc2
Date: Tue, 18 Feb 2014 11:01:46 +0000 [thread overview]
Message-ID: <20140218110145.GD4178@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <20140218105434.GO14089@laptop.programming.kicks-ass.net>
On Tue, Feb 18, 2014 at 10:54:34AM +0000, Peter Zijlstra wrote:
> On Tue, Feb 18, 2014 at 10:18:31AM +0000, Will Deacon wrote:
> > On Mon, Feb 10, 2014 at 10:17:59PM +0000, Drew Richardson wrote:
> > > While adding CPU on/offlining support during perf captures I get an
> > > Oops both on ARM as well as my desktop x86_64. Below is a small
> > > program that duplicates the issue.
> >
> > [...]
> >
> > FWIW I can reproduce this easily with -rc3 on my x86 laptop running
> > hackbench in parallel with a tweaked version of your test (using
> > _SC_NPROCESSORS_ONLN instead of _SC_NPROCESSORS_CONF and hotplugging off
> > both CPU2 and CPU3).
>
> -ENOTEST
Sorry, I trimmed it from my reply since it's not especially concise. It's
inlined in the original post:
http://lkml.kernel.org/r/20140210221758.GB11542@dreric01-Precision-T1600
Will
next prev parent reply other threads:[~2014-02-18 11:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 22:17 Perf Oops on 3.14-rc2 Drew Richardson
2014-02-18 10:18 ` Will Deacon
2014-02-18 10:52 ` Peter Zijlstra
2014-02-18 11:03 ` Will Deacon
2014-02-18 10:54 ` Peter Zijlstra
2014-02-18 11:01 ` Will Deacon [this message]
2014-02-19 16:28 ` Peter Zijlstra
2014-02-19 18:03 ` Stephane Eranian
2014-02-19 18:36 ` Peter Zijlstra
2014-02-19 19:59 ` Stephane Eranian
2014-02-19 20:24 ` Peter Zijlstra
2014-02-19 19:37 ` Drew Richardson
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=20140218110145.GD4178@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=Drew.Richardson@arm.com \
--cc=Pawel.Moll@arm.com \
--cc=Wade.Cherry@arm.com \
--cc=acme@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox