From: kernel test robot <lkp@intel.com>
To: Zhanpeng Zhang <zhangzhanpeng.jasper@bytedance.com>,
atish.patra@linux.dev, anup@brainfault.org, will@kernel.org,
palmer@dabbelt.com, pjw@kernel.org, cuiyunhui@bytedance.com
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
yuanzhu@bytedance.com,
Zhanpeng Zhang <zhangzhanpeng.jasper@bytedance.com>
Subject: Re: [PATCH] drivers/perf: riscv: do not restart throttled events after overflow
Date: Thu, 30 Apr 2026 23:23:45 +0800 [thread overview]
Message-ID: <202604302308.Wa7Tg3es-lkp@intel.com> (raw)
In-Reply-To: <20260415032017.10712-1-zhangzhanpeng.jasper@bytedance.com>
Hi Zhanpeng,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on v7.1-rc1 next-20260429]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Zhanpeng-Zhang/drivers-perf-riscv-do-not-restart-throttled-events-after-overflow/20260416-205442
base: linus/master
patch link: https://lore.kernel.org/r/20260415032017.10712-1-zhangzhanpeng.jasper%40bytedance.com
patch subject: [PATCH] drivers/perf: riscv: do not restart throttled events after overflow
config: riscv-allmodconfig (https://download.01.org/0day-ci/archive/20260430/202604302308.Wa7Tg3es-lkp@intel.com/config)
compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project 5bac06718f502014fade905512f1d26d578a18f3)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260430/202604302308.Wa7Tg3es-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202604302308.Wa7Tg3es-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/perf/riscv_pmu_sbi.c:65:33: error: use of undeclared identifier 'MAX_INTERRUPTS'
65 | return event->hw.interrupts == MAX_INTERRUPTS;
| ^~~~~~~~~~~~~~
1 error generated.
vim +/MAX_INTERRUPTS +65 drivers/perf/riscv_pmu_sbi.c
61
62 PMU_FORMAT_ATTR(event, "config:0-55");
63 static inline bool rvpmu_perf_event_is_throttled(struct perf_event *event)
64 {
> 65 return event->hw.interrupts == MAX_INTERRUPTS;
66 }
67
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-04-30 15:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 3:20 [PATCH] drivers/perf: riscv: do not restart throttled events after overflow Zhanpeng Zhang
2026-04-15 5:44 ` Michael Ellerman
2026-04-30 15:23 ` kernel test robot [this message]
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=202604302308.Wa7Tg3es-lkp@intel.com \
--to=lkp@intel.com \
--cc=anup@brainfault.org \
--cc=atish.patra@linux.dev \
--cc=cuiyunhui@bytedance.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=will@kernel.org \
--cc=yuanzhu@bytedance.com \
--cc=zhangzhanpeng.jasper@bytedance.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