linux-kernel - Re: [External] Re: [PATCH v3 8/8] drivers: firmware: riscv: add unknown nmi support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAEEQ3wkmFXAqBfHwJYbJRc5pagOJvtu-wEYGwXBF2beQiSMT1w@mail.gmail.com>
Date: Thu, 4 Dec 2025 13:18:00 +0800
From: yunhui cui <cuiyunhui@...edance.com>
To: Radim Krčmář <rkrcmar@...tanamicro.com>
Cc: conor@...nel.org, paul.walmsley@...ive.com, palmer@...belt.com, 
	aou@...s.berkeley.edu, alex@...ti.fr, luxu.kernel@...edance.com, 
	linux-kernel@...r.kernel.org, linux-riscv@...ts.infradead.org, 
	jassisinghbrar@...il.com, conor.dooley@...rochip.com, 
	valentina.fernandezalanis@...rochip.com, catalin.marinas@....com, 
	will@...nel.org, maz@...nel.org, timothy.hayes@....com, lpieralisi@...nel.org, 
	arnd@...db.de, kees@...nel.org, tglx@...utronix.de, viresh.kumar@...aro.org, 
	boqun.feng@...il.com, linux-arm-kernel@...ts.infradead.org, 
	cleger@...osinc.com, atishp@...osinc.com, ajones@...tanamicro.com, 
	linux-riscv <linux-riscv-bounces@...ts.infradead.org>
Subject: Re: [External] Re: [PATCH v3 8/8] drivers: firmware: riscv: add
 unknown nmi support

Hi Radim,

On Thu, Dec 4, 2025 at 12:11 PM Radim Krčmář <rkrcmar@...tanamicro.com> wrote:
>
> 2025-11-27T20:53:05+08:00, Yunhui Cui <cuiyunhui@...edance.com>:
> > Register unknown_nmi_handler() as the handler for the UNKNOWN_NMI
> > event. When the system becomes unresponsive, unknown_nmi_handler()
> > can be manually triggered, which in turn invokes nmi_panic() to
> > collect vmcore for root cause analysis.
>
> Is UNKNOWN_NMI what we expect the watchdog to send?

For reference: As stated in
https://github.com/riscv-non-isa/riscv-sbi-doc/pull/223, "Generally,
an external interrupt is used as an Unknown NMI pin, and an Unknown
NMI event is sent to the SBI firmware by triggering this pin. Then the
SBI firmware will send SBI_SSE_EVENT_GLOBAL_UNKNOWN_NMI to the
kernel."

When the Linux system is unresponsive, we can manually trigger it via
BMC (ipmitool).

>
> Thanks.

Thanks,
Yunhui