From: Peter Zijlstra <peterz@infradead.org>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: linux-kernel@vger.kernel.org, Borislav Petkov <bp@suse.de>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Huang Rui <ray.huang@amd.com>
Subject: Re: perf: fuzzer crashes immediately on AMD system
Date: Fri, 19 Aug 2016 12:01:30 +0200 [thread overview]
Message-ID: <20160819100130.GD10121@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1608181046120.19862@macbook-air>
On Thu, Aug 18, 2016 at 10:46:31AM -0400, Vince Weaver wrote:
> On Thu, 18 Aug 2016, Vince Weaver wrote:
>
> > Tried the perf_fuzzer on my A10 fam15h/model13h system with 4.8-rc2 and it
> > falls over more or less immediately.
> >
> > This maps to variable_test_bit()
> > called by ctx = find_get_context(pmu, task, event);
> > in kernel/events/core.c:9467
> >
> > It happens quickly enough I can probably track down the exact event that
> > causes this, if needed.
>
> I have a one line reproducer:
>
> perf stat -a -e amd_nb/config=0x37,config1=0x20/ /bin/ls
OK, cannot reproduce on my fam15h/model1h. I'll go dig through the
various manuals to see if I can spot the fail.
Huang could you either prod someone at AMD or do yourself, audit the AMD
perf code for all the various new models?
next prev parent reply other threads:[~2016-08-19 10:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 14:32 perf: fuzzer crashes immediately on AMD system Vince Weaver
2016-08-18 14:46 ` Vince Weaver
2016-08-19 10:01 ` Peter Zijlstra [this message]
2016-08-19 10:56 ` Peter Zijlstra
2016-08-19 15:03 ` Vince Weaver
2016-08-19 16:38 ` Vince Weaver
2016-08-20 4:44 ` Vince Weaver
2016-08-22 11:16 ` Huang Rui
2016-08-23 1:02 ` Vince Weaver
2016-08-23 2:54 ` Vince Weaver
2016-08-23 8:45 ` Peter Zijlstra
2016-08-23 11:53 ` Vince Weaver
2016-08-24 9:19 ` Ingo Molnar
2016-08-24 13:20 ` Vince Weaver
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=20160819100130.GD10121@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=ray.huang@amd.com \
--cc=vincent.weaver@maine.edu \
/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