From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S934829AbcIGAKK (ORCPT <rfc822;w@1wt.eu>);
        Tue, 6 Sep 2016 20:10:10 -0400
Received: from smtpauth02h.mfg.siteprotect.com ([64.26.60.151]:43880 "EHLO
        smtpauth02.mfg.siteprotect.com" rhost-flags-OK-OK-OK-FAIL)
        by vger.kernel.org with ESMTP id S933652AbcIGAKJ (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 6 Sep 2016 20:10:09 -0400
Date: Tue, 6 Sep 2016 20:13:27 -0400 (EDT)
From: Vince Weaver <vince@deater.net>
X-X-Sender: vince@pianoman.cluster.toy
To: Ingo Molnar <mingo@kernel.org>
cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>,
        Peter Zijlstra <a.p.zijlstra@chello.nl>,
        Ingo Molnar <mingo@redhat.com>, linux-kernel@vger.kernel.org,
        eranian@google.com, Arnaldo Carvalho de Melo <acme@infradead.org>,
        vincent.weaver@maine.edu
Subject: Re: [PATCH v2 0/5] perf, bts: Fallout from the fuzzer for
 perf/urgent
In-Reply-To: <20160906171915.GA8963@gmail.com>
Message-ID: <alpine.DEB.2.11.1609062009450.3432@pianoman.cluster.toy>
References: <20160906132353.19887-1-alexander.shishkin@linux.intel.com> <20160906171915.GA8963@gmail.com>
User-Agent: Alpine 2.11 (DEB 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-CTCH-Spam: Unknown
X-CTCH-RefID: str=0001.0A020204.57CF5AE0.0144,ss=1,re=0.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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