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] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 3 Apr 2019 00:31:51 +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 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.