From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760574AbcHaNlK (ORCPT ); Wed, 31 Aug 2016 09:41:10 -0400 Received: from merlin.infradead.org ([205.233.59.134]:45614 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759115AbcHaNlJ (ORCPT ); Wed, 31 Aug 2016 09:41:09 -0400 Date: Wed, 31 Aug 2016 15:41:03 +0200 From: Peter Zijlstra To: Jiri Olsa Cc: Ingo Molnar , Andi Kleen , lkml , Alexander Shishkin Subject: Re: [RFC,PATCH] VMWARE faults on accessing disabled counters Message-ID: <20160831134103.GE10153@twins.programming.kicks-ass.net> References: <20160831120358.GB9001@krava> <20160831131104.GC10153@twins.programming.kicks-ass.net> <20160831131924.GA2801@krava> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160831131924.GA2801@krava> User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Aug 31, 2016 at 03:19:24PM +0200, Jiri Olsa wrote: > > I guess if real HW does not fault on this we dont need to bother, > and treat it as the VMWARE issue.. but I couldn't find this info > So I've once had a machine that backlisted one entry, but I've forgotten what machine that was. But IIRC, you could program the thing just fine, the results were crap though, which is why CPUID blacklisted the counter. /me pokes around some code... Ah, see the AAJ80 code. That was some Nehalem part and the comment very much implies programming the value 'works', you just get crap results.