public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	 Kan Liang <kan.liang@linux.intel.com>,
	Dapeng Mi <dapeng1.mi@linux.intel.com>,
	 Jim Mattson <jmattson@google.com>,
	Jinrong Liang <cloudliang@tencent.com>,
	 Aaron Lewis <aaronlewis@google.com>,
	Like Xu <likexu@tencent.com>
Subject: [PATCH v10 09/29] KVM: x86/pmu: Disallow "fast" RDPMC for architectural Intel PMUs
Date: Tue,  9 Jan 2024 15:02:29 -0800	[thread overview]
Message-ID: <20240109230250.424295-10-seanjc@google.com> (raw)
In-Reply-To: <20240109230250.424295-1-seanjc@google.com>

Inject #GP on RDPMC if the "fast" flag is set for architectural Intel
PMUs, i.e. if the PMU version is non-zero.  Per Intel's SDM, and confirmed
on bare metal, the "fast" flag is supported only for non-architectural
PMUs, and is reserved for architectural PMUs.

  If the processor does not support architectural performance monitoring
  (CPUID.0AH:EAX[7:0]=0), ECX[30:0] specifies the index of the PMC to be
  read. Setting ECX[31] selects “fast” read mode if supported. In this mode,
  RDPMC returns bits 31:0 of the PMC in EAX while clearing EDX to zero.

  If the processor does support architectural performance monitoring
  (CPUID.0AH:EAX[7:0] ≠ 0), ECX[31:16] specifies type of PMC while ECX[15:0]
  specifies the index of the PMC to be read within that type. The following
  PMC types are currently defined:
  — General-purpose counters use type 0. The index x (to read IA32_PMCx)
    must be less than the value enumerated by CPUID.0AH.EAX[15:8] (thus
    ECX[15:8] must be zero).
  — Fixed-function counters use type 4000H. The index x (to read
    IA32_FIXED_CTRx) can be used if either CPUID.0AH.EDX[4:0] > x or
    CPUID.0AH.ECX[x] = 1 (thus ECX[15:5] must be 0).
  — Performance metrics use type 2000H. This type can be used only if
    IA32_PERF_CAPABILITIES.PERF_METRICS_AVAILABLE[bit 15]=1. For this type,
    the index in ECX[15:0] is implementation specific.

Opportunistically WARN if KVM ever actually tries to complete RDPMC for a
non-architectural PMU, and drop the non-existent "support" for fast RDPMC,
as KVM doesn't support such PMUs, i.e. kvm_pmu_rdpmc() should reject the
RDPMC before getting to the Intel code.

Fixes: f5132b01386b ("KVM: Expose a version 2 architectural PMU to a guests")
Fixes: 67f4d4288c35 ("KVM: x86: rdpmc emulation checks the counter incorrectly")
Reviewed-by: Dapeng Mi <dapeng1.mi@linux.intel.com>
Signed-off-by: Sean Christopherson <seanjc@google.com>
---
 arch/x86/kvm/vmx/pmu_intel.c | 22 ++++++++++++++++++----
 1 file changed, 18 insertions(+), 4 deletions(-)

diff --git a/arch/x86/kvm/vmx/pmu_intel.c b/arch/x86/kvm/vmx/pmu_intel.c
index 03bd188b5754..5a5dfae6055c 100644
--- a/arch/x86/kvm/vmx/pmu_intel.c
+++ b/arch/x86/kvm/vmx/pmu_intel.c
@@ -27,7 +27,6 @@
  * "fast" reads, whereas the "type" is an explicit value.
  */
 #define INTEL_RDPMC_FIXED	INTEL_PMC_FIXED_RDPMC_BASE
-#define INTEL_RDPMC_FAST	BIT(31)
 
 #define MSR_PMC_FULL_WIDTH_BIT      (MSR_IA32_PMC0 - MSR_IA32_PERFCTR0)
 
@@ -72,10 +71,25 @@ static struct kvm_pmc *intel_rdpmc_ecx_to_pmc(struct kvm_vcpu *vcpu,
 	struct kvm_pmc *counters;
 	unsigned int num_counters;
 
-	if (idx & INTEL_RDPMC_FAST)
-		*mask &= GENMASK_ULL(31, 0);
+	/*
+	 * The encoding of ECX for RDPMC is different for architectural versus
+	 * non-architecturals PMUs (PMUs with version '0').  For architectural
+	 * PMUs, bits 31:16 specify the PMC type and bits 15:0 specify the PMC
+	 * index.  For non-architectural PMUs, bit 31 is a "fast" flag, and
+	 * bits 30:0 specify the PMC index.
+	 *
+	 * Yell and reject attempts to read PMCs for a non-architectural PMU,
+	 * as KVM doesn't support such PMUs.
+	 */
+	if (WARN_ON_ONCE(!pmu->version))
+		return NULL;
 
-	idx &= ~(INTEL_RDPMC_FIXED | INTEL_RDPMC_FAST);
+	/*
+	 * Fixed PMCs are supported on all architectural PMUs.  Note, KVM only
+	 * emulates fixed PMCs for PMU v2+, but the flag itself is still valid,
+	 * i.e. let RDPMC fail due to accessing a non-existent counter.
+	 */
+	idx &= ~INTEL_RDPMC_FIXED;
 	if (fixed) {
 		counters = pmu->fixed_counters;
 		num_counters = pmu->nr_arch_fixed_counters;
-- 
2.43.0.472.g3155946c3a-goog


  parent reply	other threads:[~2024-01-09 23:03 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-09 23:02 [PATCH v10 00/29] KVM: x86/pmu: selftests: Fixes and new tests Sean Christopherson
2024-01-09 23:02 ` [PATCH v10 01/29] KVM: x86/pmu: Always treat Fixed counters as available when supported Sean Christopherson
2024-01-09 23:02 ` [PATCH v10 02/29] KVM: x86/pmu: Allow programming events that match unsupported arch events Sean Christopherson
2024-01-09 23:02 ` [PATCH v10 03/29] KVM: x86/pmu: Remove KVM's enumeration of Intel's architectural encodings Sean Christopherson
2024-01-09 23:02 ` [PATCH v10 04/29] KVM: x86/pmu: Setup fixed counters' eventsel during PMU initialization Sean Christopherson
2024-01-09 23:02 ` [PATCH v10 05/29] KVM: x86/pmu: Get eventsel for fixed counters from perf Sean Christopherson
2024-01-09 23:02 ` [PATCH v10 06/29] KVM: x86/pmu: Don't ignore bits 31:30 for RDPMC index on AMD Sean Christopherson
2024-01-09 23:02 ` [PATCH v10 07/29] KVM: x86/pmu: Prioritize VMX interception over #GP on RDPMC due to bad index Sean Christopherson
2024-01-09 23:02 ` [PATCH v10 08/29] KVM: x86/pmu: Apply "fast" RDPMC only to Intel PMUs Sean Christopherson
2024-01-09 23:02 ` Sean Christopherson [this message]
2024-01-09 23:02 ` [PATCH v10 10/29] KVM: x86/pmu: Treat "fixed" PMU type in RDPMC as index as a value, not flag Sean Christopherson
2024-01-09 23:02 ` [PATCH v10 11/29] KVM: x86/pmu: Explicitly check for RDPMC of unsupported Intel PMC types Sean Christopherson
2024-01-12  3:50   ` Mi, Dapeng
2024-01-09 23:02 ` [PATCH v10 12/29] KVM: selftests: Add vcpu_set_cpuid_property() to set properties Sean Christopherson
2024-01-09 23:02 ` [PATCH v10 13/29] KVM: selftests: Drop the "name" param from KVM_X86_PMU_FEATURE() Sean Christopherson
2024-01-09 23:02 ` [PATCH v10 14/29] KVM: selftests: Extend {kvm,this}_pmu_has() to support fixed counters Sean Christopherson
2024-01-09 23:02 ` [PATCH v10 15/29] KVM: selftests: Add pmu.h and lib/pmu.c for common PMU assets Sean Christopherson
2024-01-10  9:21   ` Andrew Jones
2024-01-10 13:58     ` Sean Christopherson
2024-01-09 23:02 ` [PATCH v10 16/29] KVM: selftests: Test Intel PMU architectural events on gp counters Sean Christopherson
2024-01-12  9:14   ` Mi, Dapeng
2024-01-12 21:37     ` Sean Christopherson
2024-01-15  2:03       ` Mi, Dapeng
2024-01-30 23:27         ` Sean Christopherson
2024-01-31  2:11           ` Mi, Dapeng
2024-01-31 15:31             ` Sean Christopherson
2024-02-01  1:51               ` Mi, Dapeng
2024-01-09 23:02 ` [PATCH v10 17/29] KVM: selftests: Test Intel PMU architectural events on fixed counters Sean Christopherson
2024-01-09 23:02 ` [PATCH v10 18/29] KVM: selftests: Test consistency of CPUID with num of gp counters Sean Christopherson
2024-01-09 23:02 ` [PATCH v10 19/29] KVM: selftests: Test consistency of CPUID with num of fixed counters Sean Christopherson
2024-01-09 23:02 ` [PATCH v10 20/29] KVM: selftests: Add functional test for Intel's fixed PMU counters Sean Christopherson
2024-01-09 23:02 ` [PATCH v10 21/29] KVM: selftests: Expand PMU counters test to verify LLC events Sean Christopherson
2024-01-09 23:02 ` [PATCH v10 22/29] KVM: selftests: Add a helper to query if the PMU module param is enabled Sean Christopherson
2024-01-09 23:02 ` [PATCH v10 23/29] KVM: selftests: Add helpers to read integer module params Sean Christopherson
2024-01-09 23:02 ` [PATCH v10 24/29] KVM: selftests: Query module param to detect FEP in MSR filtering test Sean Christopherson
2024-01-09 23:02 ` [PATCH v10 25/29] KVM: selftests: Move KVM_FEP macro into common library header Sean Christopherson
2024-01-09 23:02 ` [PATCH v10 26/29] KVM: selftests: Test PMC virtualization with forced emulation Sean Christopherson
2024-01-09 23:02 ` [PATCH v10 27/29] KVM: selftests: Add a forced emulation variation of KVM_ASM_SAFE() Sean Christopherson
2024-01-09 23:02 ` [PATCH v10 28/29] KVM: selftests: Add helpers for safe and safe+forced RDMSR, RDPMC, and XGETBV Sean Christopherson
2024-01-09 23:02 ` [PATCH v10 29/29] KVM: selftests: Extend PMU counters test to validate RDPMC after WRMSR Sean Christopherson
2024-01-12  9:17 ` [PATCH v10 00/29] KVM: x86/pmu: selftests: Fixes and new tests Mi, Dapeng
2024-01-31  0:59 ` Sean Christopherson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240109230250.424295-10-seanjc@google.com \
    --to=seanjc@google.com \
    --cc=aaronlewis@google.com \
    --cc=cloudliang@tencent.com \
    --cc=dapeng1.mi@linux.intel.com \
    --cc=jmattson@google.com \
    --cc=kan.liang@linux.intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=likexu@tencent.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox