On 11/1/2023 2:47 AM, Jim Mattson wrote:
On Tue, Oct 31, 2023 at 2:22 AM Dapeng Mi <dapeng1.mi@xxxxxxxxxxxxxxx> wrote:
Intel CPUs, like Sapphire Rapids, introduces a new fixed counter
(fixed counter 3) to counter/sample topdown.slots event, but current
code still doesn't cover this new fixed counter.
So this patch adds code to validate this new fixed counter can count
slots event correctly.
I'm not convinced that this actually validates anything.
Suppose, for example, that KVM used fixed counter 1 when the guest
asked for fixed counter 3. Wouldn't this test still pass?
Per my understanding, as long as the KVM returns a valid count in the
reasonable count range, we can think KVM works correctly. We don't need
to entangle on how KVM really uses the HW, it could be impossible and
unnecessary.
Yeah, currently the predefined valid count range may be some kind of
loose since I want to cover as much as hardwares and avoid to cause
regression. Especially after introducing the random jump and clflush
instructions, the cycles and slots become much more hard to predict.
Maybe we can have a comparable restricted count range in the initial
change, and we can loosen the restriction then if we encounter a failure
on some specific hardware. do you think it's better? Thanks.
Signed-off-by: Dapeng Mi <dapeng1.mi@xxxxxxxxxxxxxxx>
---
x86/pmu.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/x86/pmu.c b/x86/pmu.c
index 6bd8f6d53f55..404dc7b62ac2 100644
--- a/x86/pmu.c
+++ b/x86/pmu.c
@@ -47,6 +47,7 @@ struct pmu_event {
{"fixed 1", MSR_CORE_PERF_FIXED_CTR0, 10*N, 10.2*N},
{"fixed 2", MSR_CORE_PERF_FIXED_CTR0 + 1, 1*N, 500*N},
{"fixed 3", MSR_CORE_PERF_FIXED_CTR0 + 2, 0.1*N, 300*N},
+ {"fixed 4", MSR_CORE_PERF_FIXED_CTR0 + 3, 1*N, 5000*N},
};
char *buf;
--
2.34.1
