[moderation/CI] Re: KVM: x86/pmu: Add hardware Topdown metrics support
syzbot ci <[email protected]> Tue, 28 Jul 2026 11:21:14 -0700
| Newsgroups | dev.linux.lists.syzbot |
|---|---|
| Message-ID | <[email protected]> |
syzbot ci has tested the following series [v7] KVM: x86/pmu: Add hardware Topdown metrics support https://lore.kernel.org/all/[email protected] * [PATCH v7 1/9] KVM: x86/pmu: Do not map fixed counters >= 3 to generic perf events * [PATCH v7 2/9] KVM: x86/pmu: Support Intel fixed counter 3 on mediated vPMU * [PATCH v7 3/9] KVM: x86/pmu: Rename and move vcpu_get_perf_capabilities() to pmu.h * [PATCH v7 4/9] KVM: x86/pmu: Snapshot host IA32_PERF_CAPABILITIES in kvm_host * [PATCH v7 5/9] KVM: x86/pmu: Support PERF_METRICS MSR in mediated vPMU * [PATCH v7 6/9] KVM: x86/pmu: Move RDPMC emulation into per-vendor callbacks * [PATCH v7 7/9] KVM: x86/pmu: Restrict RDPMC passthrough to known CPUs * [PATCH v7 8/9] KVM: x86/pmu: Emulate RDPMC on performance metrics * [PATCH v7 9/9] KVM: selftests: Add PERF_METRICS and fixed counter 3 tests and found the following issue: kernel build error Full report is available here: https://ci.syzbot.org/series/a13c8555-bb2f-4a56-8e6e-44118c51c80c *** kernel build error tree: kvm-next URL: https://kernel.googlesource.com/pub/scm/virt/kvm/kvm/ base: a204badd8432f93b7e862e7dac6db0fe3d65f370 arch: amd64 compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8 config: https://ci.syzbot.org/builds/3201c48d-2519-42bd-9cfd-04d5c26c628e/config arch/x86/kvm/pmu.c:90:16: error: use of undeclared identifier 'INTEL_PANTHERLAKE_R' *** If these findings have caused you to resend the series or submit a separate fix, please add the following tag to your commit message: Tested-by: [email protected] --- This report is generated by a bot. It may contain errors. syzbot ci engineers can be reached at [email protected]. To test a patch for this bug, please reply with `#syz test` (should be on a separate line). The patch should be attached to the email. Note: arguments like custom git repos and branches are not supported. The email will later be sent to: [[email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]] If the report looks fine to you, reply with: #syz upstream If the report is a false positive, reply with #syz invalid