Skip to contentSkip to conversation

x86/pmu: Fix test errors on GNR/SRF/CWF

PATCH Applied Sean Christopherson 2 participants 11 messages Nov 20, 2025 – Nov 21, 2025 KVM

lore
Share & tools
lore

Sean Christopherson

author reviewer
#0 lore raw

v4 cover x86/pmu: Fix test errors on GNR/SRF/CWF

Refreshed version of Dapeng's series to address minor flaws in v3.

This patchset fixes the pmu test errors on Granite Rapids (GNR), Sierra Forest (SRF) and Clearwater Forest (CWF).

GNR and SRF start to support the timed PEBS. Timed PEBS adds a new "retired latency" field in basic info group to show the timing info and the PERF_CAPABILITIES[17] called "PEBS_TIMING_INFO" bit is added to indicated whether timed PEBS is supported. KVM module doesn't need to do any specific change to support timed PEBS except a perf change adding PERF_CAP_PEBS_TIMING_INFO flag into PERF_CAP_PEBS_MASK[1]. The patch 7/7 supports timed PEBS validation in pmu_pebs test.

On Intel Atom platforms, 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[2].

In 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.

As the overcount issue, pmu test would fail to validate the precise count for these 2 events on SRF and CWF. Patches 1-4/7 detects if the platform has this overcount issue, if so relax the precise count validation for these 2 events.

Besides it looks more LLC references are needed on SRF/CWF, so adjust the "LLC references" event count range.

Tests:
* pmu tests passed on SPR/GNR/SRF/CWF.
* pmu_lbr tests is skiped on SPR/GNR/SRF/CWF since mediated vPMU based arch-LBR support is not upstreamed yet.
* pmu_pebs test passed on SPR/GNR/SRF and skiped on CWF since CWF introduces architectural PEBS and mediated vPMU based arch-PEBS support is not upstreamed yet.

v4:
- Track the errata in pmu_caps so that the information is available to all tests (even though non-PMU tests are unlikely to care).
- Keep the measure_for_overflow() call for fixed counters.
- Handle errata independently for precise checks.

v3:
- https://lore.kernel.org/all/[email protected]
- Fix the emulated instruction validation error on SRF/CWF. (Patch 5/8)

v2:
- Fix the flaws on x86_model() helper (Xiaoyao).
- Fix the pmu_pebs error on GNR/SRF.

Dapeng Mi (3):
x86/pmu: Relax precise count check for emulated instructions tests
x86: pmu_pebs: Remove abundant data_cfg_match calculation
x86: pmu_pebs: Support to validate timed PEBS record on GNR/SRF

dongsheng (5):
x86/pmu: Add helper to detect Intel overcount issues x86/pmu: Relax precise count validation for Intel overcounted
platforms
x86/pmu: Fix incorrect masking of fixed counters
x86/pmu: Handle instruction overcount issue in overflow test x86/pmu: Expand "llc references" upper limit for broader compatibility

 lib/x86/pmu.c       | 39 ++++++++++++++++++++++++
 lib/x86/pmu.h       | 11 +++++++
 lib/x86/processor.h | 26 ++++++++++++++++
 x86/pmu.c           | 72 ++++++++++++++++++++++++++++++---------------
 x86/pmu_pebs.c      |  9 +++---
 5 files changed, 129 insertions(+), 28 deletions(-)

base-commit: de952a4bf26cb2e93c634445034645523f65d28b

Signature · 1 line
2.52.0.rc2.455.g230fcf2819-goog
author reviewer
#1 lore raw

PATCH v4 1/8 x86/pmu: Add helper to detect Intel overcount issues

From: dongsheng <[email protected]>

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.

[Rewrite comments and commit message - Dapeng]
[sean: put errata detection and tracking in pmu_init()]
---
 lib/x86/pmu.c       | 39 +++++++++++++++++++++++++++++++++++++++
 lib/x86/pmu.h       |  5 +++++
 lib/x86/processor.h | 26 ++++++++++++++++++++++++++
 3 files changed, 70 insertions(+)
lib/x86/pmu.c +39 -0
index fb46b196..67f3b23e 100644
@@ -2,11 +2,50 @@
 
 struct pmu_caps pmu;
 
+/*
+ * 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 void pmu_detect_intel_overcount_errata(void)
+{
+	struct cpuid c = cpuid(1);
+
+	if (x86_family(c.a) == 0x6) {
+		switch (x86_model(c.a)) {
+		case 0xDD: /* Clearwater Forest */
+			pmu.errata.instructions_retired_overcount = true;
+			break;
+
+		case 0xAF: /* Sierra Forest */
+		case 0x4D: /* Avaton, Rangely */
+		case 0x5F: /* Denverton */
+		case 0x86: /* Jacobsville */
+			pmu.errata.instructions_retired_overcount = true;
+			pmu.errata.branches_retired_overcount = true;
+			break;
+		default:
+			break;
+		}
+	}
+}
+
 void pmu_init(void)
 {
 	pmu.is_intel = is_intel();
 
 	if (pmu.is_intel) {
+		pmu_detect_intel_overcount_errata();
+
 		pmu.version = this_cpu_property(X86_PROPERTY_PMU_VERSION);
 
 		if (pmu.version > 1) {
lib/x86/pmu.h +5 -0
index c7dc68c1..e84b37dc 100644
@@ -73,6 +73,11 @@ struct pmu_caps {
 	u32 msr_global_status_clr;
 
 	u64 perf_cap;
+
+	struct {
+		bool instructions_retired_overcount;
+		bool branches_retired_overcount;
+	} errata;
 };
 
 extern struct pmu_caps pmu;
lib/x86/processor.h +26 -0
index 8a73af5e..68bd774b 100644
@@ -226,6 +226,32 @@ static inline bool is_intel(void)
 	return strcmp((char *)name, "GenuineIntel") == 0;
 }
 
+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;
+}
+
 /*
  * Pack the information into a 64-bit value so that each X86_FEATURE_XXX can be
  * passed by value with no overhead.
Signature · 1 line
2.52.0.rc2.455.g230fcf2819-goog
author reviewer
#2 lore raw

PATCH v4 2/8 x86/pmu: Relax precise count validation for Intel overcounted platforms

In reply to Sean Christopherson

From: dongsheng <[email protected]>

As the VM-Exit/VM-Entry overcount issue on Intel Atom platforms, there is no way to validate the precise count for "instructions" and "branches" events on these overcounted Atom platforms. Thus relax the precise count validation on these overcounted platforms.

---
 x86/pmu.c | 13 +++++++++----
 1 file changed, 9 insertions(+), 4 deletions(-)
x86/pmu.c +9 -4
index f932ccab..bd16211d 100644
@@ -229,10 +229,15 @@ static void adjust_events_range(struct pmu_event *gp_events,
 	 * occur while running the measured code, e.g. if the host takes IRQs.
 	 */
 	if (pmu.is_intel && this_cpu_has_perf_global_ctrl()) {
-		gp_events[instruction_idx].min = LOOP_INSNS;
-		gp_events[instruction_idx].max = LOOP_INSNS;
-		gp_events[branch_idx].min = LOOP_BRANCHES;
-		gp_events[branch_idx].max = LOOP_BRANCHES;
+		if (!pmu.errata.instructions_retired_overcount) {
+			gp_events[instruction_idx].min = LOOP_INSNS;
+			gp_events[instruction_idx].max = LOOP_INSNS;
+		}
+
+		if (!pmu.errata.branches_retired_overcount) {
+			gp_events[branch_idx].min = LOOP_BRANCHES;
+			gp_events[branch_idx].max = LOOP_BRANCHES;
+		}
 	}
 
 	/*
Signature · 1 line
2.52.0.rc2.455.g230fcf2819-goog
author reviewer
#3 lore raw

PATCH v4 3/8 x86/pmu: Fix incorrect masking of fixed counters

In reply to Sean Christopherson

From: dongsheng <[email protected]>

The current implementation mistakenly limits the width of fixed counters to the width of GP counters. Correct the logic to ensure fixed counters are properly masked according to their own width.

Opportunistically refine the GP counter bitwidth processing code.

[sean: keep measure_for_overflow() for fixed counter (see commit 7ec3b67a)]
---
 x86/pmu.c | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)
x86/pmu.c +5 -5
index bd16211d..96b76d04 100644
@@ -547,19 +547,19 @@ static void check_counter_overflow(void)
 		uint64_t status;
 		int idx;
 
-		cnt.count = overflow_preset;
-		if (pmu_use_full_writes())
-			cnt.count &= (1ull << pmu.gp_counter_width) - 1;
-
 		if (i == pmu.nr_gp_counters) {
 			if (!pmu.is_intel)
 				break;
 
 			cnt.ctr = fixed_events[0].unit_sel;
 			cnt.count = measure_for_overflow(&cnt);
-			cnt.count &= (1ull << pmu.gp_counter_width) - 1;
+			cnt.count &= (1ull << pmu.fixed_counter_width) - 1;
 		} else {
 			cnt.ctr = MSR_GP_COUNTERx(i);
+
+			cnt.count = overflow_preset;
+			if (pmu_use_full_writes())
+				cnt.count &= (1ull << pmu.gp_counter_width) - 1;
 		}
 
 		if (i % 2)
Signature · 1 line
2.52.0.rc2.455.g230fcf2819-goog
author reviewer
#4 lore raw

PATCH v4 4/8 x86/pmu: Handle instruction overcount issue in overflow test

In reply to Sean Christopherson

From: dongsheng <[email protected]>

During the execution of __measure(), VM exits (e.g., due to WRMSR/EXTERNAL_INTERRUPT) may occur. On systems affected by the instruction overcount issue, each VM-Exit/VM-Entry can erroneously increment the instruction count by one, leading to false failures in overflow tests.

To address this, the patch introduces a range-based validation in place of precise instruction count checks. Additionally, overflow_preset is now statically set to 1 - LOOP_INSNS, rather than being dynamically determined via measure_for_overflow().

These changes ensure consistent and predictable behavior aligned with the intended loop instruction count, while avoiding modifications to the subsequent status and status-clear testing logic.

The chosen validation range is empirically derived to maintain test reliability across hardware variations.

---
 x86/pmu.c | 23 +++++++++++++++++++++--
 1 file changed, 21 insertions(+), 2 deletions(-)
x86/pmu.c +21 -2
index 96b76d04..e1e98959 100644
@@ -510,6 +510,21 @@ static void check_counters_many(void)
 
 static uint64_t measure_for_overflow(pmu_counter_t *cnt)
 {
+	/*
+	 * During the execution of __measure(), VM exits (e.g., due to
+	 * WRMSR/EXTERNAL_INTERRUPT) may occur. On systems affected by the
+	 * instruction overcount issue, each VM-Exit/VM-Entry can erroneously
+	 * increment the instruction count by one, leading to false failures
+	 * in overflow tests.
+	 *
+	 * To mitigate this, if the overcount issue is detected, hardcode the
+	 * overflow preset to (1 - LOOP_INSNS) instead of calculating it
+	 * dynamically. This ensures that an overflow will reliably occur,
+	 * regardless of any overcounting caused by VM exits.
+	 */
+	if (pmu.errata.instructions_retired_overcount)
+		return 1 - LOOP_INSNS;
+
 	__measure(cnt, 0);
 	/*
 	 * To generate overflow, i.e. roll over to '0', the initial count just
@@ -568,8 +583,12 @@ static void check_counter_overflow(void)
 			cnt.config &= ~EVNTSEL_INT;
 		idx = event_to_global_idx(&cnt);
 		__measure(&cnt, cnt.count);
-		if (pmu.is_intel)
-			report(cnt.count == 1, "cntr-%d", i);
+		if (pmu.is_intel) {
+			if (pmu.errata.instructions_retired_overcount)
+				report(cnt.count < 14, "cntr-%d", i);
+			else
+				report(cnt.count == 1, "cntr-%d", i);
+		}
 		else
 			report(cnt.count == 0xffffffffffff || cnt.count < 7, "cntr-%d", i);
 
Signature · 1 line
2.52.0.rc2.455.g230fcf2819-goog
author reviewer
#5 lore raw

PATCH v4 5/8 x86/pmu: Relax precise count check for emulated instructions tests

In reply to Sean Christopherson

From: Dapeng Mi <[email protected]>

Relax precise count check for emulated instructions tests on these platforms with HW overcount issues.

[sean: handle errata independently]
---
 x86/pmu.c | 24 ++++++++++++------------
 1 file changed, 12 insertions(+), 12 deletions(-)
x86/pmu.c +12 -12
index e1e98959..ccf4ee63 100644
@@ -756,6 +756,8 @@ static void check_emulated_instr(void)
 		/* instructions */
 		.config = EVNTSEL_OS | EVNTSEL_USR | gp_events[instruction_idx].unit_sel,
 	};
+	const bool has_perf_global_ctrl = this_cpu_has_perf_global_ctrl();
+
 	report_prefix_push("emulated instruction");
 
 	if (this_cpu_has_perf_global_status())
@@ -769,7 +771,7 @@ static void check_emulated_instr(void)
 	wrmsr(MSR_GP_COUNTERx(0), brnch_start & gp_counter_width);
 	wrmsr(MSR_GP_COUNTERx(1), instr_start & gp_counter_width);
 
-	if (this_cpu_has_perf_global_ctrl()) {
+	if (has_perf_global_ctrl) {
 		eax = BIT(0) | BIT(1);
 		ecx = pmu.msr_global_ctl;
 		edx = 0;
@@ -784,17 +786,15 @@ static void check_emulated_instr(void)
 
 	// Check that the end count - start count is at least the expected
 	// number of instructions and branches.
-	if (this_cpu_has_perf_global_ctrl()) {
-		report(instr_cnt.count - instr_start == KVM_FEP_INSNS,
-		       "instruction count");
-		report(brnch_cnt.count - brnch_start == KVM_FEP_BRANCHES,
-		       "branch count");
-	} else {
-		report(instr_cnt.count - instr_start >= KVM_FEP_INSNS,
-		       "instruction count");
-		report(brnch_cnt.count - brnch_start >= KVM_FEP_BRANCHES,
-		       "branch count");
-	}
+	if (has_perf_global_ctrl && !pmu.errata.instructions_retired_overcount)
+		report(instr_cnt.count - instr_start == KVM_FEP_INSNS, "instruction count");
+	else
+		report(instr_cnt.count - instr_start >= KVM_FEP_INSNS, "instruction count");
+
+	if (has_perf_global_ctrl && !pmu.errata.branches_retired_overcount)
+		report(brnch_cnt.count - brnch_start == KVM_FEP_BRANCHES, "branch count");
+	else
+		report(brnch_cnt.count - brnch_start >= KVM_FEP_BRANCHES, "branch count");
 
 	if (this_cpu_has_perf_global_status()) {
 		// Additionally check that those counters overflowed properly.
Signature · 1 line
2.52.0.rc2.455.g230fcf2819-goog
author reviewer
#6 lore raw

PATCH v4 6/8 x86/pmu: Expand "llc references" upper limit for broader compatibility

In reply to Sean Christopherson

From: dongsheng <[email protected]>

Increase the upper limit of the "llc references" test to accommodate results observed on additional Intel CPU models, including CWF and SRF.
These CPUs exhibited higher reference counts that previously caused the test to fail.

---
 x86/pmu.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
x86/pmu.c +1 -1
index ccf4ee63..b262ea59 100644
@@ -116,7 +116,7 @@ struct pmu_event {
 	{"core cycles", 0x003c, 1*N, 50*N},
 	{"instructions", 0x00c0, 10*N, 10.2*N},
 	{"ref cycles", 0x013c, 1*N, 30*N},
-	{"llc references", 0x4f2e, 1, 2*N},
+	{"llc references", 0x4f2e, 1, 2.5*N},
 	{"llc misses", 0x412e, 1, 1*N},
 	{"branches", 0x00c4, 1*N, 1.1*N},
 	{"branch misses", 0x00c5, 1, 0.1*N},
Signature · 1 line
2.52.0.rc2.455.g230fcf2819-goog
author reviewer
#7 lore raw

PATCH v4 7/8 x86: pmu_pebs: Remove abundant data_cfg_match calculation

In reply to Sean Christopherson

From: Dapeng Mi <[email protected]>

Remove abundant data_cfg_match calculation.

---
 x86/pmu_pebs.c | 1 -
 1 file changed, 1 deletion(-)
x86/pmu_pebs.c +0 -1
index 6e73fc34..2848cc1e 100644
@@ -296,7 +296,6 @@ static void check_pebs_records(u64 bitmask, u64 pebs_data_cfg, bool use_adaptive
 		pebs_record_size = pebs_rec->format_size >> RECORD_SIZE_OFFSET;
 		pebs_idx_match = pebs_rec->applicable_counters & bitmask;
 		pebs_size_match = pebs_record_size == get_pebs_record_size(pebs_data_cfg, use_adaptive);
-		data_cfg_match = (pebs_rec->format_size & GENMASK_ULL(47, 0)) == pebs_data_cfg;
 		data_cfg_match = (pebs_rec->format_size & GENMASK_ULL(47, 0)) ==
 				 (use_adaptive ? pebs_data_cfg : 0);
 		expected = pebs_idx_match && pebs_size_match && data_cfg_match;
Signature · 1 line
2.52.0.rc2.455.g230fcf2819-goog
author reviewer
#8 lore raw

PATCH v4 8/8 x86: pmu_pebs: Support to validate timed PEBS record on GNR/SRF

In reply to Sean Christopherson

From: Dapeng Mi <[email protected]>

On Intel GNR/SRF platform, timed PEBS is introduced. Timed PEBS adds a new "retired latency" field in basic info group to show the timing info. IA32_PERF_CAPABILITIES.PEBS_TIMING_INFO[bit 17] is introduced to indicate whether timed PEBS is supported.

After introducing timed PEBS, the PEBS record format field shrinks to bits[31:0] and the bits[47:32] is used to record retired latency.

Thus shrink the record format to bits[31:0] accordingly and avoid the retired latency field is recognized a part of record format to compare and cause failure on GNR/SRF.

Please find detailed information about timed PEBS in section 8.4.1 "Timed Processor Event Based Sampling" of "Intel Architecture Instruction Set Extensions and Future Features".

---
 lib/x86/pmu.h  | 6 ++++++
 x86/pmu_pebs.c | 8 +++++---
 2 files changed, 11 insertions(+), 3 deletions(-)
lib/x86/pmu.h +6 -0
index e84b37dc..cd6091af 100644
@@ -20,6 +20,7 @@
 #define PMU_CAP_LBR_FMT	  0x3f
 #define PMU_CAP_FW_WRITES	(1ULL << 13)
 #define PMU_CAP_PEBS_BASELINE	(1ULL << 14)
+#define PMU_CAP_PEBS_TIMING_INFO	(1ULL << 17)
 #define PERF_CAP_PEBS_FORMAT           0xf00
 
 #define EVNSEL_EVENT_SHIFT	0
@@ -193,4 +194,9 @@ static inline bool pmu_has_pebs_baseline(void)
 	return pmu.perf_cap & PMU_CAP_PEBS_BASELINE;
 }
 
+static inline bool pmu_has_pebs_timing_info(void)
+{
+	return pmu.perf_cap & PMU_CAP_PEBS_TIMING_INFO;
+}
+
 #endif /* _X86_PMU_H_ */
x86/pmu_pebs.c +5 -3
index 2848cc1e..bc37e8e3 100644
@@ -277,6 +277,7 @@ static void check_pebs_records(u64 bitmask, u64 pebs_data_cfg, bool use_adaptive
 	unsigned int count = 0;
 	bool expected, pebs_idx_match, pebs_size_match, data_cfg_match;
 	void *cur_record;
+	u64 format_mask;
 
 	expected = (ds->pebs_index == ds->pebs_buffer_base) && !pebs_rec->format_size;
 	if (!(rdmsr(MSR_CORE_PERF_GLOBAL_STATUS) & GLOBAL_STATUS_BUFFER_OVF)) {
@@ -289,6 +290,8 @@ static void check_pebs_records(u64 bitmask, u64 pebs_data_cfg, bool use_adaptive
 		return;
 	}
 
+	/* Record format shrinks to bits[31:0] after timed PEBS is introduced. */
+	format_mask = pmu_has_pebs_timing_info() ? GENMASK_ULL(31, 0) : GENMASK_ULL(47, 0);
 	expected = ds->pebs_index >= ds->pebs_interrupt_threshold;
 	cur_record = (void *)pebs_buffer;
 	do {
@@ -296,8 +299,7 @@ static void check_pebs_records(u64 bitmask, u64 pebs_data_cfg, bool use_adaptive
 		pebs_record_size = pebs_rec->format_size >> RECORD_SIZE_OFFSET;
 		pebs_idx_match = pebs_rec->applicable_counters & bitmask;
 		pebs_size_match = pebs_record_size == get_pebs_record_size(pebs_data_cfg, use_adaptive);
-		data_cfg_match = (pebs_rec->format_size & GENMASK_ULL(47, 0)) ==
-				 (use_adaptive ? pebs_data_cfg : 0);
+		data_cfg_match = (pebs_rec->format_size & format_mask) == (use_adaptive ? pebs_data_cfg : 0);
 		expected = pebs_idx_match && pebs_size_match && data_cfg_match;
 		report(expected,
 		       "PEBS record (written seq %d) is verified (including size, counters and cfg).", count);
@@ -327,7 +329,7 @@ static void check_pebs_records(u64 bitmask, u64 pebs_data_cfg, bool use_adaptive
 			       pebs_record_size, get_pebs_record_size(pebs_data_cfg, use_adaptive));
 		if (!data_cfg_match)
 			printf("FAIL: The pebs_data_cfg (0x%lx) doesn't match with the effective MSR_PEBS_DATA_CFG (0x%lx).\n",
-			       pebs_rec->format_size & 0xffffffffffff, use_adaptive ? pebs_data_cfg : 0);
+			       pebs_rec->format_size & format_mask, use_adaptive ? pebs_data_cfg : 0);
 	}
 }
 
Signature · 1 line
2.52.0.rc2.455.g230fcf2819-goog
#9 lore raw
In reply to Sean Christopherson

Test this patch-set on SPR/SRF/CWF for both legacy vPMU and mediated vPMU, no issue is found. Thanks.

Quoted 76 lines · Sean Christopherson

Refreshed version of Dapeng's series to address minor flaws in v3.

This patchset fixes the pmu test errors on Granite Rapids (GNR), Sierra Forest (SRF) and Clearwater Forest (CWF).

GNR and SRF start to support the timed PEBS. Timed PEBS adds a new "retired latency" field in basic info group to show the timing info and the PERF_CAPABILITIES[17] called "PEBS_TIMING_INFO" bit is added to indicated whether timed PEBS is supported. KVM module doesn't need to do any specific change to support timed PEBS except a perf change adding PERF_CAP_PEBS_TIMING_INFO flag into PERF_CAP_PEBS_MASK[1]. The patch 7/7 supports timed PEBS validation in pmu_pebs test.

On Intel Atom platforms, 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[2].

In 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.

As the overcount issue, pmu test would fail to validate the precise count for these 2 events on SRF and CWF. Patches 1-4/7 detects if the platform has this overcount issue, if so relax the precise count validation for these 2 events.

Besides it looks more LLC references are needed on SRF/CWF, so adjust the "LLC references" event count range.

Tests:
* pmu tests passed on SPR/GNR/SRF/CWF.
* pmu_lbr tests is skiped on SPR/GNR/SRF/CWF since mediated vPMU based arch-LBR support is not upstreamed yet.
* pmu_pebs test passed on SPR/GNR/SRF and skiped on CWF since CWF introduces architectural PEBS and mediated vPMU based arch-PEBS support is not upstreamed yet.

v4:
- Track the errata in pmu_caps so that the information is available to all tests (even though non-PMU tests are unlikely to care).
- Keep the measure_for_overflow() call for fixed counters.
- Handle errata independently for precise checks.

v3:
- https://lore.kernel.org/all/[email protected]
- Fix the emulated instruction validation error on SRF/CWF. (Patch 5/8)

v2:
- Fix the flaws on x86_model() helper (Xiaoyao).
- Fix the pmu_pebs error on GNR/SRF.

Dapeng Mi (3):
x86/pmu: Relax precise count check for emulated instructions tests
x86: pmu_pebs: Remove abundant data_cfg_match calculation
x86: pmu_pebs: Support to validate timed PEBS record on GNR/SRF

dongsheng (5):
x86/pmu: Add helper to detect Intel overcount issues x86/pmu: Relax precise count validation for Intel overcounted
platforms
x86/pmu: Fix incorrect masking of fixed counters
x86/pmu: Handle instruction overcount issue in overflow test x86/pmu: Expand "llc references" upper limit for broader compatibility

 lib/x86/pmu.c       | 39 ++++++++++++++++++++++++
 lib/x86/pmu.h       | 11 +++++++
 lib/x86/processor.h | 26 ++++++++++++++++
 x86/pmu.c           | 72 ++++++++++++++++++++++++++++++---------------
 x86/pmu_pebs.c      |  9 +++---
 5 files changed, 129 insertions(+), 28 deletions(-)

base-commit: de952a4bf26cb2e93c634445034645523f65d28b

author reviewer Applied
#10 lore raw
In reply to Sean Christopherson
Quoted 13 lines · Sean Christopherson

Refreshed version of Dapeng's series to address minor flaws in v3.

This patchset fixes the pmu test errors on Granite Rapids (GNR), Sierra Forest (SRF) and Clearwater Forest (CWF).

GNR and SRF start to support the timed PEBS. Timed PEBS adds a new "retired latency" field in basic info group to show the timing info and the PERF_CAPABILITIES[17] called "PEBS_TIMING_INFO" bit is added to indicated whether timed PEBS is supported. KVM module doesn't need to do any specific change to support timed PEBS except a perf change adding PERF_CAP_PEBS_TIMING_INFO flag into PERF_CAP_PEBS_MASK[1]. The patch 7/7 supports timed PEBS validation in pmu_pebs test.

Quoted 1 line

[...]

Applied to kvm-x86 next, thanks!

[1/8] x86/pmu: Add helper to detect Intel overcount issues

      https://github.com/kvm-x86/kvm-unit-tests/commit/de6d1319b8aa
[2/8] x86/pmu: Relax precise count validation for Intel overcounted platforms
      https://github.com/kvm-x86/kvm-unit-tests/commit/89e3f25e00ea
[3/8] x86/pmu: Fix incorrect masking of fixed counters
      https://github.com/kvm-x86/kvm-unit-tests/commit/803637b5280d
[4/8] x86/pmu: Handle instruction overcount issue in overflow test
      https://github.com/kvm-x86/kvm-unit-tests/commit/1b09357a2737
[5/8] x86/pmu: Relax precise count check for emulated instructions tests
      https://github.com/kvm-x86/kvm-unit-tests/commit/e8ad559c361d
[6/8] x86/pmu: Expand "llc references" upper limit for broader compatibility
      https://github.com/kvm-x86/kvm-unit-tests/commit/941fcfe6e46f
[7/8] x86: pmu_pebs: Remove abundant data_cfg_match calculation
      https://github.com/kvm-x86/kvm-unit-tests/commit/de8cd74ebbaf
[8/8] x86: pmu_pebs: Support to validate timed PEBS record on GNR/SRF
      https://github.com/kvm-x86/kvm-unit-tests/commit/f561b31d3dee

--
https://github.com/kvm-x86/kvm-unit-tests/tree/next