[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.11.1609062009450.3432@pianoman.cluster.toy>
Date: Tue, 6 Sep 2016 20:13:27 -0400 (EDT)
From: Vince Weaver <vince@...ter.net>
To: Ingo Molnar <mingo@...nel.org>
cc: Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
eranian@...gle.com, Arnaldo Carvalho de Melo <acme@...radead.org>,
vincent.weaver@...ne.edu
Subject: Re: [PATCH v2 0/5] perf, bts: Fallout from the fuzzer for
perf/urgent
On Tue, 6 Sep 2016, Ingo Molnar wrote:
> > There were more bugs since the previous version, plus the BTS barriers got
> > fixed. With these patches, my testcase keeps running and no spurious NMI
> > warnings pop up any more.
>
> Could you please also run the fuzzer that Vince uses, does it now pass
> on hardware you have access to?
I ran 4.8-rc5 with these patches applied on a Skylake machine that shows
the various bts problems pretty quickly normally.
It ran a while and didn't hit any of them, but it did fall over with RCU
errors that are (probably) unrelated.
I'd have a better report but I'm having a lot of trouble getting kernel
oopses to appear on the serial console with this new install on the
skylake machine. It may not be totally systemd's fault but I am going to
blame it anyway.
Vince
Powered by blists - more mailing lists