From: "Mi, Dapeng" <dapeng1.mi@linux.intel.com>
To: Sean Christopherson <seanjc@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, Jim Mattson <jmattson@google.com>,
Mingwei Zhang <mizhang@google.com>,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH v3 9/9] KVM: VMX: Only tell perf to enable PEBS counters for fully enabled PMCs
Date: Tue, 12 May 2026 13:01:46 +0800 [thread overview]
Message-ID: <740a4e11-7f4c-444b-9ad0-2e6f4a1ccf8e@linux.intel.com> (raw)
In-Reply-To: <20260508231353.406465-10-seanjc@google.com>
On 5/9/2026 7:13 AM, Sean Christopherson wrote:
> When passing the guest's requested PEBS_ENABLE (or rather, KVM's version
> of PEBS_ENABLE on behalf of the guest), omit counters that are locally
> disable and/or don't have a perf event (due to contention), in addition to
> omitting counters that are cross-mapped in the host.
>
> In practice, this should be a nop as perf will already have disabled the
> associated counter, i.e. cpuc->pebs_enabled should have been cleared, but
> paranoia is cheap, and the existing code _looks_ wrong.
>
> Signed-off-by: Sean Christopherson <seanjc@google.com>
> ---
> arch/x86/kvm/vmx/pmu_intel.c | 30 ++++++++++++++++--------------
> arch/x86/kvm/vmx/vmx.c | 11 +----------
> arch/x86/kvm/vmx/vmx.h | 15 ++++++++++++++-
> 3 files changed, 31 insertions(+), 25 deletions(-)
>
> diff --git a/arch/x86/kvm/vmx/pmu_intel.c b/arch/x86/kvm/vmx/pmu_intel.c
> index 659fe097b904..1e420c8bca9d 100644
> --- a/arch/x86/kvm/vmx/pmu_intel.c
> +++ b/arch/x86/kvm/vmx/pmu_intel.c
> @@ -736,34 +736,36 @@ static void intel_pmu_cleanup(struct kvm_vcpu *vcpu)
> intel_pmu_release_guest_lbr_event(vcpu);
> }
>
> -u64 intel_pmu_get_cross_mapped_mask(struct kvm_pmu *pmu)
> +u64 __intel_pmu_compute_pebs_enable(struct kvm_pmu *pmu)
> {
> - u64 host_cross_mapped_mask;
> + u64 guest_pebs_enable = pmu->pebs_enable & pmu->global_ctrl;
> + u64 pebs_enable = 0;
> struct kvm_pmc *pmc;
> int bit, hw_idx;
>
> /*
> - * Provide a mask of counters that are cross-mapped between the guest
> - * and the host, i.e. where a guest PMC is mapped to a host PMC with a
> - * different index. PEBS records hold a PERF_GLOBAL_STATUS snapshot,
> - * and so PEBS-enabled counters need to hold the correct index so as
> - * not to confuse the guest.
> + * Omit counters that are locally disabled, don't have a perf event, or
> + * ended up with a perf event that is using a different counter than
> + * the guest, i.e. where the guest PMC is different than the host PMC
> + * being used on behalf of the guest. PEBS records include
> + * PERF_GLOBAL_STATUS, and so using a counter with a different index
> + * means the guest will see overflow status for the wrong counter(s).
> */
> - host_cross_mapped_mask = 0;
> -
> - kvm_for_each_pmc(pmu, pmc, bit, (unsigned long *)&pmu->global_ctrl) {
> + kvm_for_each_pmc(pmu, pmc, bit, (unsigned long *)&guest_pebs_enable) {
> if (!pmc_is_locally_enabled(pmc) || !pmc->perf_event)
> continue;
>
> /*
> - * A negative index indicates the event isn't mapped to a
> + * Note, a negative index indicates the event isn't mapped to a
> * physical counter in the host, e.g. due to contention.
> */
> hw_idx = pmc->perf_event->hw.idx;
> - if (hw_idx != pmc->idx && hw_idx > -1)
> - host_cross_mapped_mask |= BIT_ULL(hw_idx);
> + if (hw_idx != pmc->idx)
> + continue;
> +
> + pebs_enable |= BIT_ULL(pmc->idx);
> }
> - return host_cross_mapped_mask;
> + return pebs_enable;
> }
>
> static bool intel_pmu_is_mediated_pmu_supported(struct x86_pmu_capability *host_pmu)
> diff --git a/arch/x86/kvm/vmx/vmx.c b/arch/x86/kvm/vmx/vmx.c
> index fbe3ce5f5a51..31675e5cf563 100644
> --- a/arch/x86/kvm/vmx/vmx.c
> +++ b/arch/x86/kvm/vmx/vmx.c
> @@ -7314,20 +7314,11 @@ static void atomic_switch_perf_msrs(struct vcpu_vmx *vmx)
> return;
>
> struct x86_guest_pebs guest_pebs = {
> - .enable = pmu->pebs_enable,
> + .enable = intel_pmu_compute_pebs_enable(pmu),
> .ds_area = pmu->ds_area,
> .data_cfg = pmu->pebs_data_cfg,
> };
>
> - /*
> - * Disable counters where the guest PMC is different than the host PMC
> - * being used on behalf of the guest, as the PEBS record includes
> - * PERF_GLOBAL_STATUS, i.e. the guest will see overflow status for the
> - * wrong counter(s).
> - */
> - if (guest_pebs.enable & pmu->global_ctrl)
> - guest_pebs.enable &= ~intel_pmu_get_cross_mapped_mask(pmu);
> -
> /* Note, nr_msrs may be garbage if perf_guest_get_msrs() returns NULL. */
> msrs = perf_guest_get_msrs(&nr_msrs, &guest_pebs);
> if (!msrs)
> diff --git a/arch/x86/kvm/vmx/vmx.h b/arch/x86/kvm/vmx/vmx.h
> index 0c4563472940..b055731efd2d 100644
> --- a/arch/x86/kvm/vmx/vmx.h
> +++ b/arch/x86/kvm/vmx/vmx.h
> @@ -659,7 +659,20 @@ static __always_inline struct vcpu_vmx *to_vmx(struct kvm_vcpu *vcpu)
> return container_of(vcpu, struct vcpu_vmx, vcpu);
> }
>
> -u64 intel_pmu_get_cross_mapped_mask(struct kvm_pmu *pmu);
> +u64 __intel_pmu_compute_pebs_enable(struct kvm_pmu *pmu);
> +
> +static inline u64 intel_pmu_compute_pebs_enable(struct kvm_pmu *pmu)
> +{
> + /*
> + * Avoid the function call overhead in the common case that the guest
> + * isn't using PEBS.
> + */
> + if (!(pmu->pebs_enable & pmu->global_ctrl))
> + return 0;
> +
> + return __intel_pmu_compute_pebs_enable(pmu);
> +}
> +
> int intel_pmu_create_guest_lbr_event(struct kvm_vcpu *vcpu);
> void vmx_passthrough_lbr_msrs(struct kvm_vcpu *vcpu);
Reviewed-by: Dapeng Mi <dapeng1.mi@linux.intel.com>
>
prev parent reply other threads:[~2026-05-12 5:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 23:13 [PATCH v3 0/9] perf/x86: Don't write PEBS_ENABLED on KVM transitions Sean Christopherson
2026-05-08 23:13 ` [PATCH v3 1/9] perf/x86/intel: Ensure guest PEBS path doesn't set unwanted PERF_GLOBAL_CTRL bits Sean Christopherson
2026-05-12 4:53 ` Mi, Dapeng
2026-05-08 23:13 ` [PATCH v3 2/9] perf/x86/intel: Don't write PEBS_ENABLED on host<=>guest xfers if CPU has isolation Sean Christopherson
2026-05-12 4:53 ` Mi, Dapeng
2026-05-08 23:13 ` [PATCH v3 3/9] perf/x86/intel: Don't context switch DS_AREA (and PEBS config) if PEBS is unused Sean Christopherson
2026-05-08 23:13 ` [PATCH v3 4/9] perf/x86/intel: Make @data a mandatory param for intel_guest_get_msrs() Sean Christopherson
2026-05-12 12:39 ` Jim Mattson
2026-05-08 23:13 ` [PATCH v3 5/9] perf/x86/intel: Invert names of intel_ctrl_{guest,host}_mask Sean Christopherson
2026-05-12 4:58 ` Mi, Dapeng
2026-05-08 23:13 ` [PATCH v3 6/9] perf/x86: KVM: Have perf define a dedicated struct for getting guest PEBS data Sean Christopherson
2026-05-08 23:13 ` [PATCH v3 7/9] perf/x86/intel: KVM: Handle cross-mapped PEBS PMCs entirely within KVM Sean Christopherson
2026-05-12 4:59 ` Mi, Dapeng
2026-05-08 23:13 ` [PATCH v3 8/9] KVM: VMX: Drop a redundant pmu->global_ctrl check when processing pebs_enable Sean Christopherson
2026-05-12 5:00 ` Mi, Dapeng
2026-05-08 23:13 ` [PATCH v3 9/9] KVM: VMX: Only tell perf to enable PEBS counters for fully enabled PMCs Sean Christopherson
2026-05-12 5:01 ` Mi, Dapeng [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=740a4e11-7f4c-444b-9ad0-2e6f4a1ccf8e@linux.intel.com \
--to=dapeng1.mi@linux.intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jmattson@google.com \
--cc=jolsa@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=mizhang@google.com \
--cc=namhyung@kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=seanjc@google.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