Return-Path: Received: from mail.linutronix.de (146.0.238.70:993) by crypto-ml.lab.linutronix.de with IMAP4-SSL for ; 07 Feb 2019 22:07:06 -0000 Received: from mga18.intel.com ([134.134.136.126]) by Galois.linutronix.de with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1grrp2-0004vc-Fx for speck@linutronix.de; Thu, 07 Feb 2019 23:07:05 +0100 Date: Thu, 7 Feb 2019 14:04:50 -0800 From: Andi Kleen Subject: [MODERATED] Re: [PATCH v2 0/8] PERFv2 Message-ID: <20190207220450.GU31598@tassilo.jf.intel.com> References: <20190207132709.GA32477@hirez.programming.kicks-ass.net> <20190207143759.GP31598@tassilo.jf.intel.com> <20190207153728.GE32477@hirez.programming.kicks-ass.net> <2875fb7c-1354-c401-a7e5-6cb2cb02b40c@citrix.com> <20190207170059.GD32511@hirez.programming.kicks-ass.net> MIME-Version: 1.0 In-Reply-To: <20190207170059.GD32511@hirez.programming.kicks-ass.net> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: speck@linutronix.de List-ID: > > This feature and MSR are not architectural, and not expected to exist on > > future hardware with a silicon fix for the issue (CascadeLake B1 > > stepping and later, IIRC). If you really want to migrate you could just make it a noop. After all the other CPUs have all counters always working. > > PMU deliberately > > isn't available to guests in general, That's a sad attitude, but luckily less and less true in real deployments. > > profiling/other can trivially flip the default. > > Is that a per-guest or per-hv setting? My current patch does per-hv, but > I suppose it would not be too hard to make that per-guest. The only > question is where/how does the guest communicate this desire. The right way to communicate is to set the MSR. -Andi