All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Radim Krčmář" <rkrcmar@ventanamicro.com>
To: "Yunhui Cui" <cuiyunhui@bytedance.com>, <conor@kernel.org>,
	<paul.walmsley@sifive.com>, <palmer@dabbelt.com>,
	<aou@eecs.berkeley.edu>, <alex@ghiti.fr>,
	<luxu.kernel@bytedance.com>, <linux-kernel@vger.kernel.org>,
	<linux-riscv@lists.infradead.org>, <jassisinghbrar@gmail.com>,
	<conor.dooley@microchip.com>,
	<valentina.fernandezalanis@microchip.com>,
	<catalin.marinas@arm.com>, <will@kernel.org>, <maz@kernel.org>,
	<timothy.hayes@arm.com>, <lpieralisi@kernel.org>, <arnd@arndb.de>,
	<kees@kernel.org>, <tglx@linutronix.de>,
	<viresh.kumar@linaro.org>, <boqun.feng@gmail.com>,
	<linux-arm-kernel@lists.infradead.org>, <cleger@rivosinc.com>,
	<atishp@rivosinc.com>, <ajones@ventanamicro.com>
Cc: "linux-riscv" <linux-riscv-bounces@lists.infradead.org>
Subject: Re: [PATCH v3 8/8] drivers: firmware: riscv: add unknown nmi support
Date: Thu, 04 Dec 2025 13:11:39 +0900	[thread overview]
Message-ID: <DEP50CD8K22E.1JW7GL6WLK44W@ventanamicro.com> (raw)
In-Reply-To: <20251127125305.89961-9-cuiyunhui@bytedance.com>

2025-11-27T20:53:05+08:00, Yunhui Cui <cuiyunhui@bytedance.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.


WARNING: multiple messages have this Message-ID (diff)
From: "Radim Krčmář" <rkrcmar@ventanamicro.com>
To: "Yunhui Cui" <cuiyunhui@bytedance.com>, <conor@kernel.org>,
	<paul.walmsley@sifive.com>, <palmer@dabbelt.com>,
	<aou@eecs.berkeley.edu>, <alex@ghiti.fr>,
	<luxu.kernel@bytedance.com>, <linux-kernel@vger.kernel.org>,
	<linux-riscv@lists.infradead.org>, <jassisinghbrar@gmail.com>,
	<conor.dooley@microchip.com>,
	<valentina.fernandezalanis@microchip.com>,
	<catalin.marinas@arm.com>, <will@kernel.org>, <maz@kernel.org>,
	<timothy.hayes@arm.com>, <lpieralisi@kernel.org>, <arnd@arndb.de>,
	<kees@kernel.org>, <tglx@linutronix.de>,
	<viresh.kumar@linaro.org>, <boqun.feng@gmail.com>,
	<linux-arm-kernel@lists.infradead.org>, <cleger@rivosinc.com>,
	<atishp@rivosinc.com>, <ajones@ventanamicro.com>
Cc: "linux-riscv" <linux-riscv-bounces@lists.infradead.org>
Subject: Re: [PATCH v3 8/8] drivers: firmware: riscv: add unknown nmi support
Date: Thu, 04 Dec 2025 13:11:39 +0900	[thread overview]
Message-ID: <DEP50CD8K22E.1JW7GL6WLK44W@ventanamicro.com> (raw)
In-Reply-To: <20251127125305.89961-9-cuiyunhui@bytedance.com>

2025-11-27T20:53:05+08:00, Yunhui Cui <cuiyunhui@bytedance.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.

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2025-12-04  4:11 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-27 12:52 [PATCH v3 0/8] Add NMI Support to RISC-V via SSE Yunhui Cui
2025-11-27 12:52 ` Yunhui Cui
2025-11-27 12:52 ` [PATCH v3 1/8] drivers: firmware: riscv: add SSE NMI support Yunhui Cui
2025-11-27 12:52   ` Yunhui Cui
2025-11-27 12:52 ` [PATCH v3 2/8] riscv: smp: move ipi_cpu_crash_stop() declaration to smp.h Yunhui Cui
2025-11-27 12:52   ` Yunhui Cui
2025-11-27 12:53 ` [PATCH v3 3/8] smp: move num_other_online_cpus() into smp.h Yunhui Cui
2025-11-27 12:53   ` Yunhui Cui
2025-11-27 12:53 ` [PATCH v3 4/8] riscv: smp: use NMI for crash stop Yunhui Cui
2025-11-27 12:53   ` Yunhui Cui
2025-11-27 12:53 ` [PATCH v3 5/8] riscv: smp: use NMI for CPU stop Yunhui Cui
2025-11-27 12:53   ` Yunhui Cui
2025-12-04  4:07   ` Radim Krčmář
2025-12-04  4:07     ` Radim Krčmář
2025-12-04  5:28     ` [External] " yunhui cui
2025-12-04  5:28       ` yunhui cui
2025-12-04 13:16       ` Radim Krčmář
2025-12-04 13:16         ` Radim Krčmář
2025-12-08 11:40         ` yunhui cui
2025-12-08 11:40           ` yunhui cui
2025-12-10 14:22           ` Radim Krčmář
2025-12-10 14:22             ` Radim Krčmář
2025-12-12  3:09             ` yunhui cui
2025-12-12  3:09               ` yunhui cui
2025-11-27 12:53 ` [PATCH v3 6/8] riscv: smp: use NMI for backtrace Yunhui Cui
2025-11-27 12:53   ` Yunhui Cui
2025-11-27 12:53 ` [PATCH v3 7/8] riscv: smp: kgdb: use NMI for CPU roundup Yunhui Cui
2025-11-27 12:53   ` Yunhui Cui
2025-11-27 12:53 ` [PATCH v3 8/8] drivers: firmware: riscv: add unknown nmi support Yunhui Cui
2025-11-27 12:53   ` Yunhui Cui
2025-12-04  4:11   ` Radim Krčmář [this message]
2025-12-04  4:11     ` Radim Krčmář
2025-12-04  5:18     ` [External] " yunhui cui
2025-12-04  5:18       ` yunhui cui
2025-12-04 13:26       ` Radim Krčmář
2025-12-04 13:26         ` Radim Krčmář

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=DEP50CD8K22E.1JW7GL6WLK44W@ventanamicro.com \
    --to=rkrcmar@ventanamicro.com \
    --cc=ajones@ventanamicro.com \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=arnd@arndb.de \
    --cc=atishp@rivosinc.com \
    --cc=boqun.feng@gmail.com \
    --cc=catalin.marinas@arm.com \
    --cc=cleger@rivosinc.com \
    --cc=conor.dooley@microchip.com \
    --cc=conor@kernel.org \
    --cc=cuiyunhui@bytedance.com \
    --cc=jassisinghbrar@gmail.com \
    --cc=kees@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv-bounces@lists.infradead.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=lpieralisi@kernel.org \
    --cc=luxu.kernel@bytedance.com \
    --cc=maz@kernel.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=tglx@linutronix.de \
    --cc=timothy.hayes@arm.com \
    --cc=valentina.fernandezalanis@microchip.com \
    --cc=viresh.kumar@linaro.org \
    --cc=will@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.