public inbox for linux-perf-users@vger.kernel.org
 help / color / mirror / Atom feed
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>,
	Thomas Gleixner <tglx@kernel.org>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org, Paolo Bonzini <pbonzini@redhat.com>
Cc: 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 v2 2/4] perf/x86/intel: Don't context switch DS_AREA (and PEBS config) if PEBS is unused
Date: Mon, 27 Apr 2026 10:24:20 +0800	[thread overview]
Message-ID: <9d318656-3faf-479c-817f-f32f7d5caaae@linux.intel.com> (raw)
In-Reply-To: <20260423150340.463896-3-seanjc@google.com>


On 4/23/2026 11:03 PM, Sean Christopherson wrote:
> When filling the list of MSRs to be loaded by KVM on VM-Enter and VM-Exit,
> load the guest values for DS_AREA and (conditionally) MSR_PEBS_DATA_CFG if
> and only if PEBS will be active in the guest, i.e. only if a PEBS record
> may be generated while running the guest.  As shown by the !pebs_ept path,
> it's perfectly safe to run with the host's DS_AREA, so long as PEBS-enabled
> counters are disabled via PERF_GLOBAL_CTRL.
>
> Omitting DS_AREA and MSR_PEBS_DATA_CFG when PEBS is unused saves two MSR
> writes per MSR on each VMX transition, i.e. eliminates two/four pointless
> MSR writes on each VMX roundtrip when PEBS isn't being used by the guest.
>
> Fixes: c59a1f106f5c ("KVM: x86/pmu: Add IA32_PEBS_ENABLE MSR emulation for extended PEBS")
> Cc: Jim Mattson <jmattson@google.com>
> Cc: Mingwei Zhang <mizhang@google.com>
> Cc: Stephane Eranian <eranian@google.com>
> Reviewed-by: Jim Mattson <jmattson@google.com>
> Signed-off-by: Sean Christopherson <seanjc@google.com>
> ---
>  arch/x86/events/intel/core.c | 39 +++++++++++++++++++++++-------------
>  1 file changed, 25 insertions(+), 14 deletions(-)
>
> diff --git a/arch/x86/events/intel/core.c b/arch/x86/events/intel/core.c
> index 002d809f82ef..407fd392fd46 100644
> --- a/arch/x86/events/intel/core.c
> +++ b/arch/x86/events/intel/core.c
> @@ -5037,23 +5037,14 @@ static struct perf_guest_switch_msr *intel_guest_get_msrs(int *nr, void *data)
>  		return arr;
>  	}
>  
> +	/*
> +	 * If the guest won't use PEBS or the CPU doesn't support PEBS in the
> +	 * guest, then there's nothing more to do as disabling PMCs via
> +	 * PERF_GLOBAL_CTRL is sufficient on CPUs with guest/host isolation.
> +	 */
>  	if (!kvm_pmu || !x86_pmu.pebs_ept)
>  		return arr;
>  
> -	arr[(*nr)++] = (struct perf_guest_switch_msr){
> -		.msr = MSR_IA32_DS_AREA,
> -		.host = (unsigned long)cpuc->ds,
> -		.guest = kvm_pmu->ds_area,
> -	};
> -
> -	if (x86_pmu.intel_cap.pebs_baseline) {
> -		arr[(*nr)++] = (struct perf_guest_switch_msr){
> -			.msr = MSR_PEBS_DATA_CFG,
> -			.host = cpuc->active_pebs_data_cfg,
> -			.guest = kvm_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
> @@ -5065,6 +5056,26 @@ static struct perf_guest_switch_msr *intel_guest_get_msrs(int *nr, void *data)
>  	if (pebs_mask & ~cpuc->intel_ctrl_guest_mask)
>  		guest_pebs_mask = 0;
>  
> +	/*
> +	 * Context switch DS_AREA and PEBS_DATA_CFG if and only if PEBS will be
> +	 * active in the guest; if no records will be generated while the guest
> +	 * is running, then simply keep the host values resident in hardware.
> +	 */
> +	arr[(*nr)++] = (struct perf_guest_switch_msr){
> +		.msr = MSR_IA32_DS_AREA,
> +		.host = (unsigned long)cpuc->ds,
> +		.guest = guest_pebs_mask ? kvm_pmu->ds_area : (unsigned long)cpuc->ds,
> +	};

The code looks good to me.

one nit: people may be curious on why set same host value for guest if they
don't notice that the same value on host and guest would lead to the MSRs
would be removed from MSR load-list. Maybe add comments to further explain it.

Reviewed-by: Dapeng Mi <dapeng1.mi@linux.intel.com>

Thanks.


> +
> +	if (x86_pmu.intel_cap.pebs_baseline) {
> +		arr[(*nr)++] = (struct perf_guest_switch_msr){
> +			.msr = MSR_PEBS_DATA_CFG,
> +			.host = cpuc->active_pebs_data_cfg,
> +			.guest = guest_pebs_mask ? kvm_pmu->pebs_data_cfg :
> +						   cpuc->active_pebs_data_cfg,
> +		};
> +	}
> +
>  	/*
>  	 * Do NOT mess with PEBS_ENABLED.  As above, disabling counters via
>  	 * PERF_GLOBAL_CTRL is sufficient, and loading a stale PEBS_ENABLED,

  reply	other threads:[~2026-04-27  2:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-23 15:03 [PATCH v2 0/4] perf/x86: Don't write PEBS_ENABLED on KVM transitions Sean Christopherson
2026-04-23 15:03 ` [PATCH v2 1/4] perf/x86/intel: Don't write PEBS_ENABLED on host<=>guest xfers if CPU has isolation Sean Christopherson
2026-04-23 16:22   ` Peter Zijlstra
2026-04-23 17:59   ` Jim Mattson
2026-04-27  2:10     ` Mi, Dapeng
2026-04-27 18:07       ` Sean Christopherson
2026-04-28  2:32         ` Mi, Dapeng
2026-04-23 15:03 ` [PATCH v2 2/4] perf/x86/intel: Don't context switch DS_AREA (and PEBS config) if PEBS is unused Sean Christopherson
2026-04-27  2:24   ` Mi, Dapeng [this message]
2026-04-27 17:34     ` Sean Christopherson
2026-04-23 15:03 ` [PATCH v2 3/4] perf/x86/intel: Make @data a mandatory param for intel_guest_get_msrs() Sean Christopherson
2026-04-27  2:28   ` Mi, Dapeng
2026-04-23 15:03 ` [PATCH v2 4/4] perf/x86: KVM: Have perf define a dedicated struct for getting guest PEBS data Sean Christopherson
2026-04-23 18:14   ` Jim Mattson
2026-04-23 23:31   ` sashiko-bot
2026-04-27 17:37     ` Sean Christopherson
2026-04-23 15:33 ` [PATCH v2 0/4] perf/x86: Don't write PEBS_ENABLED on KVM transitions Jim Mattson
2026-04-23 16:16 ` Peter Zijlstra
2026-04-24 12:17   ` Mi, Dapeng
2026-04-24 12:23     ` Peter Zijlstra

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=9d318656-3faf-479c-817f-f32f7d5caaae@linux.intel.com \
    --to=dapeng1.mi@linux.intel.com \
    --cc=acme@kernel.org \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=eranian@google.com \
    --cc=jmattson@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=mizhang@google.com \
    --cc=namhyung@kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=peterz@infradead.org \
    --cc=seanjc@google.com \
    --cc=tglx@kernel.org \
    --cc=x86@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