From: "Chen, Zide" <zide.chen@intel.com>
To: Jim Mattson <jmattson@google.com>
Cc: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
kvm@vger.kernel.org, Andi Kleen <ak@linux.intel.com>,
Stephane Eranian <eranian@google.com>,
linux-kernel@vger.kernel.org, Mingwei Zhang <mizhang@google.com>,
Das Sandipan <Sandipan.Das@amd.com>,
Shukla Manali <Manali.Shukla@amd.com>,
Dapeng Mi <dapeng1.mi@linux.intel.com>,
Xudong Hao <xudong.hao@intel.com>
Subject: Re: [PATCH v9 12/12] KVM: x86/pmu: Support RDPMC Metrics Clear Mode
Date: Tue, 27 Oct 2026 17:17:19 -0500 [thread overview]
Message-ID: <48d57624-b10c-4548-b082-7fc3fcfbab10@intel.com> (raw)
In-Reply-To: <20261023185544.3305206-1-jmattson@google.com>
On 10/23/2026 1:55 PM, Jim Mattson wrote:
> On Fri, Sep 18, 2026 at 12:39 PM Zide Chen <zide.chen@intel.com> wrote:
>>
>> + pmc = kvm_pmc_idx_to_pmc(pmu, INTEL_PMC_IDX_FIXED_SLOTS);
>> + if (pmc && intel_pmu_metrics_clear_enabled(pmu)) {
>
> If kvm_vcpu_has_perf_metrics() requires fixed counter 3 (see my reply
> to 5/12), pmc can't be NULL here.
Agreed. If kvm_vcpu_has_perf_metrics() requires FC3, then the NULL check
can be dropped.
> [...]
>
>> + if (perf_capabilities & PERF_CAP_RDPMC_METRICS_CLEAR)
>> + pmu->fixed_ctr_ctrl_rsvd &=
>> + ~intel_fixed_bits_by_idx(INTEL_FIXED_SLOTS_IDX,
>> + INTEL_FIXED_3_METRICS_CLEAR);
>
> This should be predicated on the guest actually having fixed counter 3
> (and PERF_METRICS). intel_pmu_enable_fixed_counter_bits() only unmasks
> bits for counters below nr_arch_fixed_counters.
Yes, since now FC3 check is added to kvm_vcpu_has_perf_metrics(), then
it makes sense to gate the unmasking on it as well.
>
> [...]
>
>> + if ((data & PERF_CAP_RDPMC_METRICS_CLEAR) &&
>> + !(data & PERF_CAP_PERF_METRICS))
>> + return 1;
>
> If IA32_FIXED_CTR_CTRL.METRICS_CLEAR_EN[14] is only unmasked when the
> vCPU has PERF_METRICS, is this check still necessary? KVM generally
> doesn't police userspace's feature combinations unless it has to.
Agreed, dropped this check from vmx_set_msr(). Since intel_pmu_refresh()
gates unmasking METRICS_CLEAR_EN on kvm_vcpu_has_perf_metrics(vcpu),
userspace setting RDPMC_METRICS_CLEAR without PERF_METRICS will simply
have no effect and bit 14 remains reserved for the guest.
prev parent reply other threads:[~2026-10-27 22:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 19:39 [PATCH v9 00/12] KVM: x86/pmu: Add hardware Topdown metrics support Zide Chen
2026-09-18 19:39 ` [PATCH v9 01/12] KVM: x86/pmu: Do not map fixed counters >= 3 to generic perf events Zide Chen
2026-09-18 19:39 ` [PATCH v9 02/12] KVM: x86/pmu: Support Intel fixed counter 3 on mediated vPMU Zide Chen
2026-09-18 19:39 ` [PATCH v9 03/12] KVM: x86/pmu: Rename and move vcpu_get_perf_capabilities() to pmu.h Zide Chen
2026-09-18 19:39 ` [PATCH v9 04/12] KVM: x86/pmu: Snapshot host IA32_PERF_CAPABILITIES in kvm_host Zide Chen
2026-09-18 19:39 ` [PATCH v9 05/12] KVM: x86/pmu: Support PERF_METRICS MSR in mediated vPMU Zide Chen
2026-10-23 18:27 ` Jim Mattson
2026-10-27 21:30 ` Chen, Zide
2026-09-18 19:39 ` [PATCH v9 06/12] KVM: x86/pmu: Move RDPMC emulation into per-vendor callbacks Zide Chen
2026-09-18 19:39 ` [PATCH v9 07/12] KVM: x86/pmu: Emulate RDPMC on performance metrics Zide Chen
2026-10-23 18:33 ` Jim Mattson
2026-09-18 19:39 ` [PATCH v9 08/12] KVM: selftests: Add PERF_METRICS and fixed counter 3 tests Zide Chen
2026-09-18 19:39 ` [PATCH v9 09/12] perf/x86: Add INTEL_TD_METRIC_FIELD_{BITS,MASK} constants Zide Chen
2026-09-21 7:01 ` Mi, Dapeng
2026-10-27 21:39 ` Chen, Zide
2026-09-18 19:39 ` [PATCH v9 10/12] perf/x86: Expose number of Topdown metric events to KVM Zide Chen
2026-09-21 7:06 ` Mi, Dapeng
2026-09-18 19:39 ` [PATCH v9 11/12] KVM: x86/pmu: Reject writes to reserved MSR_PERF_METRICS bits Zide Chen
2026-09-21 7:11 ` Mi, Dapeng
2026-10-23 18:45 ` Jim Mattson
2026-10-27 22:09 ` Chen, Zide
2026-09-18 19:39 ` [PATCH v9 12/12] KVM: x86/pmu: Support RDPMC Metrics Clear Mode Zide Chen
2026-10-23 18:55 ` Jim Mattson
2026-10-27 22:17 ` Chen, Zide [this message]
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=48d57624-b10c-4548-b082-7fc3fcfbab10@intel.com \
--to=zide.chen@intel.com \
--cc=Manali.Shukla@amd.com \
--cc=Sandipan.Das@amd.com \
--cc=ak@linux.intel.com \
--cc=dapeng1.mi@linux.intel.com \
--cc=eranian@google.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mizhang@google.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=seanjc@google.com \
--cc=xudong.hao@intel.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
all inboxes | Powered by JetHome®