linux-kernel - Re: [RFC PATCH v3 0/3] x86/perf/amd: AMD PMC counters and NMI latency

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20190403150026.GF1421@uranus.lan>
Date:   Wed, 3 Apr 2019 18:00:26 +0300
From:   Cyrill Gorcunov <gorcunov@...il.com>
To:     Vince Weaver <vince@...ter.net>
Cc:     Peter Zijlstra <peterz@...radead.org>,
        "Lendacky, Thomas" <Thomas.Lendacky@....com>,
        "x86@...nel.org" <x86@...nel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Arnaldo Carvalho de Melo <acme@...nel.org>,
        Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
        Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
        Namhyung Kim <namhyung@...nel.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Jiri Olsa <jolsa@...hat.com>,
        Stephane Eranian <eranian@...gle.com>
Subject: Re: [RFC PATCH v3 0/3] x86/perf/amd: AMD PMC counters and NMI latency

On Wed, Apr 03, 2019 at 05:27:54PM +0300, Cyrill Gorcunov wrote:
> On Wed, Apr 03, 2019 at 10:15:33AM -0400, Vince Weaver wrote:
> > > Mind to point me where json events should lay, I could try to convert
> > > names.
> > 
> > I was mostly joking about that.  But the event lists are in the kernel 
> > tree in
> > 	tools/perf/pmu-events/arch/x86/
> >
> > I don't think anything older than Nehalem is included.
> 
> I see ;)
> 
> > After letting the fuzzer run a bit longer I did manage to get it 
> > to hard-lock with no messages in the log, though eventually while I was 
> > fiddling with alt-sysrq over serial port did get this to trigger.
> > Though if I'm going to start reporting p4 crashes I should start a 
> > separate thread.
> 
> Oh. Will try to take a look on, thanks a lot!

Btw, Vince, is there a chance to fetch last seuqence the
fuzzer inserted into events input?