From: kernel test robot <lkp@intel.com>
To: Rui Qi <qirui.001@bytedance.com>,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, alex@ghiti.fr, cyrilbur@tenstorrent.com,
tglx@kernel.org, peterz@infradead.org, debug@rivosinc.com,
andybnac@gmail.com, charlie@rivosinc.com, geomatsi@gmail.com,
thuth@redhat.com, bjorn@rivosinc.com, songshuaishuai@tinylab.org,
martin@kaiser.cx, masahiroy@kernel.org, kees@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, linux-arch@vger.kernel.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
Rui Qi <qirui.001@bytedance.com>
Subject: Re: [PATCH] riscv: add system error interrupt handler support
Date: Fri, 27 Feb 2026 03:09:28 +0800 [thread overview]
Message-ID: <202602270355.h8QSG2vl-lkp@intel.com> (raw)
In-Reply-To: <20260226082735.56108-1-qirui.001@bytedance.com>
Hi Rui,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on tip/smp/core v7.0-rc1 next-20260226]
[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/Rui-Qi/riscv-add-system-error-interrupt-handler-support/20260226-163131
base: linus/master
patch link: https://lore.kernel.org/r/20260226082735.56108-1-qirui.001%40bytedance.com
patch subject: [PATCH] riscv: add system error interrupt handler support
config: riscv-randconfig-r064-20260226 (https://download.01.org/0day-ci/archive/20260227/202602270355.h8QSG2vl-lkp@intel.com/config)
compiler: riscv32-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260227/202602270355.h8QSG2vl-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/202602270355.h8QSG2vl-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from arch/riscv/include/asm/errata_list.h:8,
from arch/riscv/include/asm/vdso/processor.h:8,
from include/vdso/processor.h:10,
from arch/riscv/include/asm/processor.h:13,
from arch/riscv/include/asm/cmpxchg.h:16,
from arch/riscv/include/asm/barrier.h:14,
from include/asm-generic/bitops/generic-non-atomic.h:7,
from include/linux/bitops.h:28,
from include/linux/kernel.h:23,
from arch/riscv/kernel/sys_error.c:7:
arch/riscv/kernel/sys_error.c: In function 'riscv_serror_starting_cpu':
>> arch/riscv/kernel/sys_error.c:28:22: error: 'RV_IRQ_SYS_ERROR' undeclared (first use in this function); did you mean 'IRQ_SYS_ERROR'?
csr_set(CSR_IE, BIT(RV_IRQ_SYS_ERROR));
^~~~~~~~~~~~~~~~
arch/riscv/include/asm/csr.h:588:38: note: in definition of macro 'csr_set'
unsigned long __v = (unsigned long)(val); \
^~~
arch/riscv/kernel/sys_error.c:28:18: note: in expansion of macro 'BIT'
csr_set(CSR_IE, BIT(RV_IRQ_SYS_ERROR));
^~~
arch/riscv/kernel/sys_error.c:28:22: note: each undeclared identifier is reported only once for each function it appears in
csr_set(CSR_IE, BIT(RV_IRQ_SYS_ERROR));
^~~~~~~~~~~~~~~~
arch/riscv/include/asm/csr.h:588:38: note: in definition of macro 'csr_set'
unsigned long __v = (unsigned long)(val); \
^~~
arch/riscv/kernel/sys_error.c:28:18: note: in expansion of macro 'BIT'
csr_set(CSR_IE, BIT(RV_IRQ_SYS_ERROR));
^~~
arch/riscv/kernel/sys_error.c: In function 'riscv_serror_dying_cpu':
arch/riscv/kernel/sys_error.c:35:24: error: 'RV_IRQ_SYS_ERROR' undeclared (first use in this function); did you mean 'IRQ_SYS_ERROR'?
csr_clear(CSR_IE, BIT(RV_IRQ_SYS_ERROR));
^~~~~~~~~~~~~~~~
arch/riscv/include/asm/csr.h:605:38: note: in definition of macro 'csr_clear'
unsigned long __v = (unsigned long)(val); \
^~~
arch/riscv/kernel/sys_error.c:35:20: note: in expansion of macro 'BIT'
csr_clear(CSR_IE, BIT(RV_IRQ_SYS_ERROR));
^~~
arch/riscv/kernel/sys_error.c: In function 'sys_error_init':
arch/riscv/kernel/sys_error.c:52:51: error: 'RV_IRQ_SYS_ERROR' undeclared (first use in this function); did you mean 'IRQ_SYS_ERROR'?
riscv_sys_error_irq = irq_create_mapping(domain, RV_IRQ_SYS_ERROR);
^~~~~~~~~~~~~~~~
IRQ_SYS_ERROR
vim +28 arch/riscv/kernel/sys_error.c
25
26 static int riscv_serror_starting_cpu(unsigned int cpu)
27 {
> 28 csr_set(CSR_IE, BIT(RV_IRQ_SYS_ERROR));
29 enable_percpu_irq(riscv_sys_error_irq, irq_get_trigger_type(riscv_sys_error_irq));
30 return 0;
31 }
32
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-02-26 19:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 8:27 [PATCH] riscv: add system error interrupt handler support Rui Qi
2026-02-26 9:22 ` Conor Dooley
2026-02-27 7:54 ` Rui Qi
2026-02-27 10:08 ` Conor Dooley
2026-03-02 2:41 ` Rui Qi
2026-02-26 19:09 ` 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=202602270355.h8QSG2vl-lkp@intel.com \
--to=lkp@intel.com \
--cc=alex@ghiti.fr \
--cc=andybnac@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=bjorn@rivosinc.com \
--cc=charlie@rivosinc.com \
--cc=cyrilbur@tenstorrent.com \
--cc=debug@rivosinc.com \
--cc=geomatsi@gmail.com \
--cc=kees@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=martin@kaiser.cx \
--cc=masahiroy@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=peterz@infradead.org \
--cc=qirui.001@bytedance.com \
--cc=songshuaishuai@tinylab.org \
--cc=tglx@kernel.org \
--cc=thuth@redhat.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