From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Vince Weaver <vince@deater.net>
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: Wed, 3 Apr 2019 00:31:51 +0300 [thread overview]
Message-ID: <20190402213151.GC23501@uranus> (raw)
In-Reply-To: <alpine.DEB.2.21.1904021709340.24692@pianoman.cluster.toy>
On Tue, Apr 02, 2019 at 05:13:15PM -0400, Vince Weaver wrote:
>
> > You know, running fuzzer on p4 might worth in anycase. As to potential
> > problems to fix -- i could try find some time slot for, still quite
> > limited too 'cause of many other duties :(
>
>
> Well I fired up the Pentium 4
> /dev/sda1 has gone 1457 days without being checked
Heh :)
> and eventually got it up to date (running "git pull" in a 5-year old Linux
> tree plus running "apt-get dist-upgrade" at the same time was maybe a
> mistake on a system with 1GB of RAM).
>
> Anyway I have it fuzzing current git and surprisingly while it's hit a few
> WARNINGs and some NMI dazed+confused messages it hasn't actually crashed
> yet. Not sure if I want to let it fuzz overnight if I'm not here though.
Wow, sounds impressive! Ping me if you find something.
>
> Shame on Intel though for not providing perf JSON files for the
> Pentium 4 event names.
Mind to point me where json events should lay, I could try to convert
names.
next prev parent reply other threads:[~2019-04-02 21:31 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
2019-04-02 15:09 ` Cyrill Gorcunov
2019-04-02 21:13 ` Vince Weaver
2019-04-02 21:31 ` Cyrill Gorcunov [this message]
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=20190402213151.GC23501@uranus \
--to=gorcunov@gmail.com \
--cc=Thomas.Lendacky@amd.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=bp@alien8.de \
--cc=eranian@google.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=vince@deater.net \
--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 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).