From: syzbot ci <syzbot+cic88c5c5505cf8153@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: KVM: x86/pmu: Add hardware Topdown metrics support
Date: Tue, 28 Jul 2026 11:21:14 -0700 [thread overview]
Message-ID: <6a68f31a.d9e86bb5.297b12.003a.GAE@google.com> (raw)
syzbot ci has tested the following series
[v7] KVM: x86/pmu: Add hardware Topdown metrics support
https://lore.kernel.org/all/20260727192131.582105-1-zide.chen@intel.com
* [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: syzbot@syzkaller.appspotmail.com
---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzkaller@googlegroups.com.
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:
[ak@linux.intel.com dapeng1.mi@linux.intel.com jmattson@google.com kvm@vger.kernel.org linux-kernel@vger.kernel.org manali.shukla@amd.com mizhang@google.com pbonzini@redhat.com sandipan.das@amd.com seanjc@google.com thomas.falcon@intel.com xudong.hao@intel.com zide.chen@intel.com]
If the report looks fine to you, reply with:
#syz upstream
If the report is a false positive, reply with
#syz invalid
reply other threads:[~2026-07-28 18:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6a68f31a.d9e86bb5.297b12.003a.GAE@google.com \
--to=syzbot+cic88c5c5505cf8153@syzkaller.appspotmail.com \
--cc=syzbot@lists.linux.dev \
--cc=syzkaller-upstream-moderation@googlegroups.com \
/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