[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <DEP50CD8K22E.1JW7GL6WLK44W@ventanamicro.com>
Date: Thu, 04 Dec 2025 13:11:39 +0900
From: Radim Krčmář <rkrcmar@...tanamicro.com>
To: "Yunhui Cui" <cuiyunhui@...edance.com>, <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>
Cc: "linux-riscv" <linux-riscv-bounces@...ts.infradead.org>
Subject: Re: [PATCH v3 8/8] drivers: firmware: riscv: add unknown nmi
support
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?
Thanks.
Powered by blists - more mailing lists