Return-Path: Received: from mail.linutronix.de (146.0.238.70:993) by crypto-ml.lab.linutronix.de with IMAP4-SSL for ; 05 Feb 2019 15:28:10 -0000 Received: from merlin.infradead.org ([2001:8b0:10b:1231::1]) by Galois.linutronix.de with esmtps (TLS1.2:RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1gr2ds-0000Nn-Sn for speck@linutronix.de; Tue, 05 Feb 2019 16:28:09 +0100 Received: from j217100.upc-j.chello.nl ([24.132.217.100] helo=hirez.programming.kicks-ass.net) by merlin.infradead.org with esmtpsa (Exim 4.90_1 #2 (Red Hat Linux)) id 1gr2dp-0004ZW-Ps for speck@linutronix.de; Tue, 05 Feb 2019 15:28:07 +0000 Date: Tue, 5 Feb 2019 16:28:04 +0100 From: Peter Zijlstra Subject: [MODERATED] Re: [PATCH v1 9/9] PERFv1 3 Message-ID: <20190205152804.GY17528@hirez.programming.kicks-ass.net> References: MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: speck@linutronix.de List-ID: On Mon, Feb 04, 2019 at 05:14:10PM -0800, speck for Andi Kleen wrote: > From: Andi Kleen > Subject: kvm: vmx: Support TSX_FORCE_ABORT in KVM guests > > Recent microcode for Skylake added a new CPUID bit and MSR to control > TSX aborting and enabling PMU counter 3. This patch adds support > for controlling counter 3 from KVM guests. > > The implementation is similar to how SPEC_CTRL is implemented. Initially > the MSR is just intercepted, to avoid any impact on the entry/exit. > When the guest uses the MSR the first time add the MSR to the > entry/exit list to context switch it against the host. > What this does not explain is how the guest can ever possibly use this correctly, since it doesn't have access to PMC3.