From: "Chen, Zide" <zide.chen@intel.com>
To: sashiko-reviews@lists.linux.dev
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH v9 08/12] KVM: selftests: Add PERF_METRICS and fixed counter 3 tests
Date: Fri, 18 Sep 2026 15:45:53 -0500 [thread overview]
Message-ID: <52d94f44-e047-4453-9adb-4192c4f925f0@intel.com> (raw)
In-Reply-To: <20260918200815.2CC4E1F000FF@smtp.kernel.org>
On 9/18/2026 3:08 PM, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] selftests: unconditional MSR read causes assertion failure on older kernels
> --
>
> commit c5ae582e90bae306393c4bf2f37f04a11e37ba5f
> Author: Zide Chen <zide.chen@intel.com>
>
> KVM: selftests: Add PERF_METRICS and fixed counter 3 tests
>
> This commit adds a test case to exercise IA32_PERF_METRICS for Topdown Level
> 1 metrics. It also extends the PMU selftest to cover Intel fixed counter 3 by
> bumping the maximum number of fixed counters and validating functionality.
>
>> diff --git a/tools/testing/selftests/kvm/x86/pmu_counters_test.c b/tools/testing/selftests/kvm/x86/pmu_counters_test.c
>> --- a/tools/testing/selftests/kvm/x86/pmu_counters_test.c
>> +++ b/tools/testing/selftests/kvm/x86/pmu_counters_test.c
> [ ... ]
>> @@ -653,8 +657,85 @@ static void test_fixed_counters(u8 pmu_version, u64 perf_capabilities)
> [ ... ]
>> static void test_intel_counters(void)
>> {
>> + u64 advertised_perf_caps = kvm_get_feature_msr(MSR_IA32_PERF_CAPABILITIES);
>
> [Severity: Medium]
> Will this unconditional MSR read cause an assertion failure on older kernels?
>
> When running the selftest on a host kernel prior to 5.9, KVM does not
> expose MSR_IA32_PERF_CAPABILITIES as a feature MSR. Calling
> kvm_get_feature_msr() unconditionally in test_intel_counters() causes the
> underlying ioctl to fail and return 0, which triggers an assertion failure
> rather than skipping the feature gracefully.
>
> Other MSR accesses in this file appear to be guarded by checking
> kvm_has_perf_caps first. Could we apply a similar check before reading
> advertised_perf_caps so the test remains compatible with older environments?
Yes, you are right. It should be guarded with kvm_has_perf_caps.
>> u8 pmu_version = kvm_cpu_property(X86_PROPERTY_PMU_VERSION);
>> unsigned int i;
>> u8 v;
> [ ... ]
>
next prev parent reply other threads:[~2026-09-18 20:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 19:39 [PATCH v9 00/12] KVM: x86/pmu: Add hardware Topdown metrics support Zide Chen
2026-09-18 19:39 ` [PATCH v9 01/12] KVM: x86/pmu: Do not map fixed counters >= 3 to generic perf events Zide Chen
2026-09-18 19:39 ` [PATCH v9 02/12] KVM: x86/pmu: Support Intel fixed counter 3 on mediated vPMU Zide Chen
2026-09-18 19:39 ` [PATCH v9 03/12] KVM: x86/pmu: Rename and move vcpu_get_perf_capabilities() to pmu.h Zide Chen
2026-09-18 19:39 ` [PATCH v9 04/12] KVM: x86/pmu: Snapshot host IA32_PERF_CAPABILITIES in kvm_host Zide Chen
2026-09-18 19:39 ` [PATCH v9 05/12] KVM: x86/pmu: Support PERF_METRICS MSR in mediated vPMU Zide Chen
2026-09-18 19:39 ` [PATCH v9 06/12] KVM: x86/pmu: Move RDPMC emulation into per-vendor callbacks Zide Chen
2026-09-18 19:39 ` [PATCH v9 07/12] KVM: x86/pmu: Emulate RDPMC on performance metrics Zide Chen
2026-09-18 19:39 ` [PATCH v9 08/12] KVM: selftests: Add PERF_METRICS and fixed counter 3 tests Zide Chen
2026-09-18 20:08 ` sashiko-bot
2026-09-18 20:45 ` Chen, Zide [this message]
2026-09-18 19:39 ` [PATCH v9 09/12] perf/x86: Add INTEL_TD_METRIC_FIELD_{BITS,MASK} constants Zide Chen
2026-09-18 19:59 ` sashiko-bot
2026-09-18 20:45 ` Chen, Zide
2026-09-21 7:01 ` Mi, Dapeng
2026-09-18 19:39 ` [PATCH v9 10/12] perf/x86: Expose number of Topdown metric events to KVM Zide Chen
2026-09-21 7:06 ` Mi, Dapeng
2026-09-18 19:39 ` [PATCH v9 11/12] KVM: x86/pmu: Reject writes to reserved MSR_PERF_METRICS bits Zide Chen
2026-09-21 7:11 ` Mi, Dapeng
2026-09-18 19:39 ` [PATCH v9 12/12] KVM: x86/pmu: Support RDPMC Metrics Clear Mode Zide Chen
2026-09-18 20:22 ` sashiko-bot
2026-09-18 21:08 ` Chen, Zide
2026-09-21 9:39 ` Mi, Dapeng
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=52d94f44-e047-4453-9adb-4192c4f925f0@intel.com \
--to=zide.chen@intel.com \
--cc=kvm@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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