From: Sandipan Das <sandipan.das@amd.com>
To: Jim Mattson <jmattson@google.com>,
seanjc@google.com, pbonzini@redhat.com
Cc: kvm@vger.kernel.org, likexu@tencent.com, yosry@kernel.org
Subject: Re: [PATCH] KVM: x86/pmu: Move Intel PMU global MSRs to intel_is_valid_msr()
Date: Thu, 3 Sep 2026 11:22:25 +0530 [thread overview]
Message-ID: <cfd5168b-80dd-49d9-b88d-3634c20bac09@amd.com> (raw)
In-Reply-To: <20260902184711.138538-1-jmattson@google.com>
On 03-09-2026 00:17, Jim Mattson wrote:
> Commit c85cdc1cc1ea ("KVM: x86/pmu: Move handling PERF_GLOBAL_CTRL and
> friends to common x86") moved the existence check for the following Intel
> PMU MSRs to kvm_pmu_is_valid_msr():
> - MSR_CORE_PERF_GLOBAL_STATUS
> - MSR_CORE_PERF_GLOBAL_CTRL
> - MSR_CORE_PERF_GLOBAL_OVF_CTRL
>
> That commit deemed these MSRs valid whenever pmu->version > 1. It intended
> to share the check with AMD PerfMonV2 because both vendor implementations
> require version 2 or greater for global PMU controls. However, as noted in
> the commit message, AMD uses different MSR indices for its global PMU
> registers.
>
> Commit 4a2771895ca6 ("KVM: x86/svm/pmu: Add AMD PerfMonV2 support")
> subsequently added AMD PerfMonV2 support and set pmu->version = 2. Because
> kvm_pmu_is_valid_msr() validated the Intel MSRs whenever pmu->version > 1,
> KVM incorrectly permitted AMD guests with PerfMonV2 to access these Intel
> MSRs without a #GP.
>
> Move the validation of these Intel MSRs to intel_is_valid_msr() and remove
> the common switch statement from kvm_pmu_is_valid_msr(). AMD already
> validates its own global PMU MSRs in amd_is_valid_msr().
>
> Fixes: 4a2771895ca6 ("KVM: x86/svm/pmu: Add AMD PerfMonV2 support")
> Signed-off-by: Jim Mattson <jmattson@google.com>
> ---
> arch/x86/kvm/pmu.c | 8 --------
> arch/x86/kvm/vmx/pmu_intel.c | 3 +++
> 2 files changed, 3 insertions(+), 8 deletions(-)
>
> diff --git a/arch/x86/kvm/pmu.c b/arch/x86/kvm/pmu.c
> index a7d60c8785cd..d2fd47ee5ec8 100644
> --- a/arch/x86/kvm/pmu.c
> +++ b/arch/x86/kvm/pmu.c
> @@ -823,14 +823,6 @@ void kvm_pmu_deliver_pmi(struct kvm_vcpu *vcpu)
>
> bool kvm_pmu_is_valid_msr(struct kvm_vcpu *vcpu, u32 msr)
> {
> - switch (msr) {
> - case MSR_CORE_PERF_GLOBAL_STATUS:
> - case MSR_CORE_PERF_GLOBAL_CTRL:
> - case MSR_CORE_PERF_GLOBAL_OVF_CTRL:
> - return kvm_pmu_has_perf_global_ctrl(vcpu_to_pmu(vcpu));
> - default:
> - break;
> - }
> return kvm_pmu_call(msr_idx_to_pmc)(vcpu, msr) ||
> kvm_pmu_call(is_valid_msr)(vcpu, msr);
> }
> diff --git a/arch/x86/kvm/vmx/pmu_intel.c b/arch/x86/kvm/vmx/pmu_intel.c
> index bfa8612fb450..70a8c4816135 100644
> --- a/arch/x86/kvm/vmx/pmu_intel.c
> +++ b/arch/x86/kvm/vmx/pmu_intel.c
> @@ -187,6 +187,9 @@ static bool intel_is_valid_msr(struct kvm_vcpu *vcpu, u32 msr)
> int ret;
>
> switch (msr) {
> + case MSR_CORE_PERF_GLOBAL_STATUS:
> + case MSR_CORE_PERF_GLOBAL_CTRL:
> + case MSR_CORE_PERF_GLOBAL_OVF_CTRL:
> case MSR_CORE_PERF_FIXED_CTR_CTRL:
> return kvm_pmu_has_perf_global_ctrl(pmu);
> case MSR_IA32_PEBS_ENABLE:
Reviewed-by: Sandipan Das <sandipan.das@amd.com>
next prev parent reply other threads:[~2026-09-03 5:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 18:47 [PATCH] KVM: x86/pmu: Move Intel PMU global MSRs to intel_is_valid_msr() Jim Mattson
2026-09-03 5:52 ` Sandipan Das [this message]
2026-09-03 6:57 ` Like Xu
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=cfd5168b-80dd-49d9-b88d-3634c20bac09@amd.com \
--to=sandipan.das@amd.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=likexu@tencent.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=yosry@kernel.org \
/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