From: Vince Weaver <vince@deater.net>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
"Lendacky, Thomas" <Thomas.Lendacky@amd.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Namhyung Kim <namhyung@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Jiri Olsa <jolsa@redhat.com>,
Stephane Eranian <eranian@google.com>
Subject: Re: [RFC PATCH v3 0/3] x86/perf/amd: AMD PMC counters and NMI latency
Date: Tue, 2 Apr 2019 10:53:38 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.21.1904021050090.15645@pianoman.cluster.toy> (raw)
In-Reply-To: <20190402132200.GA23501@uranus>
On Tue, 2 Apr 2019, Cyrill Gorcunov wrote:
> On Tue, Apr 02, 2019 at 03:03:02PM +0200, Peter Zijlstra wrote:
> > I have vague memories of the P4 thing crashing with Vince's perf_fuzzer,
> > but maybe I'm wrong.
>
> No, you're correct. p4 was crashing many times before we manage to make
> it more-less stable. The main problem though that to find working p4 box
> is really a problem.
I do have some a functioning p4 system I can test on.
I can easily run the fuzzer and report crashes, but I only have limited
time/skills to actually fix the problems it turns up.
One nice thing is that as of Linux 5.0 *finally* the fuzzer can run
indefinitely on most modern Intel chips without crashing (still triggers a
few warnings). So finally we have the ability to tell when a new crash is
a regression and potentially can bisect it. Although obviously this
doesn't necessarily apply to the p4.
I do think the number of people trying to run perf on a p4 is probably
pretty small these days.
Vince
next prev parent reply other threads:[~2019-04-02 15:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 21:46 [RFC PATCH v3 0/3] x86/perf/amd: AMD PMC counters and NMI latency Lendacky, Thomas
2019-04-01 21:46 ` [RFC PATCH v3 1/3] x86/perf/amd: Resolve race condition when disabling PMC Lendacky, Thomas
2019-04-01 21:46 ` [RFC PATCH v3 2/3] x86/perf/amd: Resolve NMI latency issues for active PMCs Lendacky, Thomas
2019-04-01 21:46 ` [RFC PATCH v3 3/3] x86/perf/amd: Remove need to check "running" bit in NMI handler Lendacky, Thomas
2019-04-02 13:03 ` [RFC PATCH v3 0/3] x86/perf/amd: AMD PMC counters and NMI latency Peter Zijlstra
2019-04-02 13:09 ` Lendacky, Thomas
2019-04-02 13:22 ` Cyrill Gorcunov
2019-04-02 14:53 ` Vince Weaver [this message]
2019-04-02 15:09 ` Cyrill Gorcunov
2019-04-02 21:13 ` Vince Weaver
2019-04-02 21:31 ` Cyrill Gorcunov
2019-04-03 14:15 ` Vince Weaver
2019-04-03 14:27 ` Cyrill Gorcunov
2019-04-03 15:00 ` Cyrill Gorcunov
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=alpine.DEB.2.21.1904021050090.15645@pianoman.cluster.toy \
--to=vince@deater.net \
--cc=Thomas.Lendacky@amd.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=bp@alien8.de \
--cc=eranian@google.com \
--cc=gorcunov@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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.