[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aR-VtupdTy4vHvSz@google.com>
Date: Thu, 20 Nov 2025 14:27:02 -0800
From: Sean Christopherson <seanjc@...gle.com>
To: Dapeng Mi <dapeng1.mi@...ux.intel.com>
Cc: Paolo Bonzini <pbonzini@...hat.com>, kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
Jim Mattson <jmattson@...gle.com>, Mingwei Zhang <mizhang@...gle.com>,
Zide Chen <zide.chen@...el.com>, Das Sandipan <Sandipan.Das@....com>,
Shukla Manali <Manali.Shukla@....com>, Xiaoyao Li <xiaoyao.li@...el.com>,
Dapeng Mi <dapeng1.mi@...el.com>, dongsheng <dongsheng.x.zhang@...el.com>,
Yi Lai <yi1.lai@...el.com>
Subject: Re: [kvm-unit-tests patch v3 1/8] x86/pmu: Add helper to detect Intel
overcount issues
On Wed, Sep 03, 2025, Dapeng Mi wrote:
> From: dongsheng <dongsheng.x.zhang@...el.com>
>
> For Intel Atom CPUs, the PMU events "Instruction Retired" or
> "Branch Instruction Retired" may be overcounted for some certain
> instructions, like FAR CALL/JMP, RETF, IRET, VMENTRY/VMEXIT/VMPTRLD
> and complex SGX/SMX/CSTATE instructions/flows.
>
> The detailed information can be found in the errata (section SRF7):
> https://edc.intel.com/content/www/us/en/design/products-and-solutions/processors-and-chipsets/sierra-forest/xeon-6700-series-processor-with-e-cores-specification-update/errata-details/
>
> For the Atom platforms before Sierra Forest (including Sierra Forest),
> Both 2 events "Instruction Retired" and "Branch Instruction Retired" would
> be overcounted on these certain instructions, but for Clearwater Forest
> only "Instruction Retired" event is overcounted on these instructions.
>
> So add a helper detect_inst_overcount_flags() to detect whether the
> platform has the overcount issue and the later patches would relax the
> precise count check by leveraging the gotten overcount flags from this
> helper.
>
> Signed-off-by: dongsheng <dongsheng.x.zhang@...el.com>
> [Rewrite comments and commit message - Dapeng]
> Signed-off-by: Dapeng Mi <dapeng1.mi@...ux.intel.com>
> Tested-by: Yi Lai <yi1.lai@...el.com>
> ---
> lib/x86/processor.h | 27 ++++++++++++++++++++++++++
> x86/pmu.c | 47 +++++++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 74 insertions(+)
>
> diff --git a/lib/x86/processor.h b/lib/x86/processor.h
> index 62f3d578..937f75e4 100644
> --- a/lib/x86/processor.h
> +++ b/lib/x86/processor.h
> @@ -1188,4 +1188,31 @@ static inline bool is_lam_u57_enabled(void)
> return !!(read_cr3() & X86_CR3_LAM_U57);
> }
>
> +/* Copy from kernel arch/x86/lib/cpu.c */
Eh, just drop this, we don't care if the kernel code changes, this is all based
on architectural behavior.
> +static inline u32 x86_family(u32 sig)
> +{
> + u32 x86;
> +
> + x86 = (sig >> 8) & 0xf;
> +
> + if (x86 == 0xf)
> + x86 += (sig >> 20) & 0xff;
> +
> + return x86;
> +}
> +
> +static inline u32 x86_model(u32 sig)
> +{
> + u32 fam, model;
> +
> + fam = x86_family(sig);
> +
> + model = (sig >> 4) & 0xf;
> +
> + if (fam >= 0x6)
> + model += ((sig >> 16) & 0xf) << 4;
> +
> + return model;
> +}
We should place these up near is_intel() so that it's more obviously what "family"
and "model" mean (should be obvious already, but it's an easy thing to do).
> +/*
> + * For Intel Atom CPUs, the PMU events "Instruction Retired" or
> + * "Branch Instruction Retired" may be overcounted for some certain
> + * instructions, like FAR CALL/JMP, RETF, IRET, VMENTRY/VMEXIT/VMPTRLD
> + * and complex SGX/SMX/CSTATE instructions/flows.
> + *
> + * The detailed information can be found in the errata (section SRF7):
> + * https://edc.intel.com/content/www/us/en/design/products-and-solutions/processors-and-chipsets/sierra-forest/xeon-6700-series-processor-with-e-cores-specification-update/errata-details/
> + *
> + * For the Atom platforms before Sierra Forest (including Sierra Forest),
> + * Both 2 events "Instruction Retired" and "Branch Instruction Retired" would
> + * be overcounted on these certain instructions, but for Clearwater Forest
> + * only "Instruction Retired" event is overcounted on these instructions.
> + */
> +static u32 detect_inst_overcount_flags(void)
> +{
> + u32 flags = 0;
> + struct cpuid c = cpuid(1);
> +
> + if (x86_family(c.a) == 0x6) {
> + switch (x86_model(c.a)) {
> + case 0xDD: /* Clearwater Forest */
> + flags = INST_RETIRED_OVERCOUNT;
> + break;
> +
> + case 0xAF: /* Sierra Forest */
> + case 0x4D: /* Avaton, Rangely */
> + case 0x5F: /* Denverton */
> + case 0x86: /* Jacobsville */
> + flags = INST_RETIRED_OVERCOUNT | BR_RETIRED_OVERCOUNT;
> + break;
> + }
> + }
> +
> + return flags;
> +}
The errata tracking definitely belongs "struct pmu_caps pmu", and the init in
pmu_init().
Powered by blists - more mailing lists