From: Andrew Morton <akpm@linux-foundation.org>
To: Pnina Feder <pnina.feder@mobileye.com>
Cc: Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] panic/kexec: Allow forcing panic execution on a specific CPU
Date: Sat, 3 Jan 2026 10:29:27 -0800 [thread overview]
Message-ID: <20260103102927.7add52a51ed0623c6e8bc729@linux-foundation.org> (raw)
In-Reply-To: <20260101123237.277411-1-pnina.feder@mobileye.com>
On Thu, 1 Jan 2026 14:32:37 +0200 Pnina Feder <pnina.feder@mobileye.com> wrote:
> Some platforms require panic handling to execute on a specific CPU
> for crash dump to work reliably. This may be due to firmware,
> interrupt routing, or platform-specific constraints where only one
> CPU is able to safely enter the crash kernel.
>
> Add an optional configuration that allows redirecting panic execution
> to a designated target CPU before invoking kexec into the crash kernel.
>
> When CONFIG_PANIC_FORCE_CPU is enabled, the initial panic CPU will
> forward the panic to the configured CPU using smp_call_function_single().
> If a panic is already in progress on another CPU, redirection is
> skipped and a warning is printed.
Requiring a recompile/reinstall isn't very user-friendly. Is it
possible to do this with a kernel boot option?
next prev parent reply other threads:[~2026-01-03 18:29 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-01 12:32 Pnina Feder
2026-01-03 18:29 ` Andrew Morton [this message]
2026-01-04 10:44 ` kernel test robot
2026-01-04 20:42 ` [PATCH v2] panic: add panic_force_cpu= parameter to redirect panic to " Pnina Feder
2026-01-05 23:34 ` Andrew Morton
2026-01-07 21:27 ` Pnina Feder
2026-01-05 8:18 ` [PATCH v3] " Pnina Feder
2026-01-05 16:50 ` Petr Mladek
2026-01-07 21:27 ` Pnina Feder
2026-01-07 21:56 ` [PATCH v4] " Pnina Feder
2026-01-07 23:10 ` Andrew Morton
2026-01-08 11:49 ` Pnina Feder
2026-01-08 3:11 ` Baoquan He
2026-01-08 7:49 ` Peter Zijlstra
2026-01-08 12:02 ` Pnina Feder
2026-01-08 7:48 ` Peter Zijlstra
2026-01-08 16:36 ` Steven Rostedt
2026-01-08 20:14 ` Pnina Feder
2026-01-08 20:09 ` Pnina Feder
2026-01-12 7:49 ` Peter Zijlstra
2026-01-14 21:57 ` Pnina Feder
2026-01-09 1:18 ` kernel test robot
2026-01-08 20:36 ` [PATCH v5] " Pnina Feder
2026-01-08 21:00 ` Steven Rostedt
2026-01-11 10:05 ` Pnina Feder
2026-01-11 17:13 ` Steven Rostedt
2026-01-09 22:19 ` kernel test robot
2026-01-09 22:41 ` Andrew Morton
2026-01-11 10:09 ` Pnina Feder
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=20260103102927.7add52a51ed0623c6e8bc729@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=pnina.feder@mobileye.com \
--cc=senozhatsky@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®