From: Petr Mladek <pmladek@suse.com>
To: Pnina Feder <pnina.feder@mobileye.com>
Cc: akpm@linux-foundation.org, bhe@redhat.com,
linux-kernel@vger.kernel.org, lkp@intel.com, mgorman@suse.de,
mingo@redhat.com, peterz@infradead.org, rostedt@goodmis.org,
senozhatsky@chromium.org, tglx@linutronix.de,
vkondra@mobileye.com
Subject: Re: [PATCH v8] panic: add panic_force_cpu= parameter to redirect panic to a specific CPU
Date: Thu, 29 Jan 2026 17:21:02 +0100 [thread overview]
Message-ID: <aXuIcrRvkhwITdWI@pathway.suse.cz> (raw)
In-Reply-To: <20260122102457.1154599-1-pnina.feder@mobileye.com>
On Thu 2026-01-22 12:24:57, Pnina Feder wrote:
> Some platforms require panic handling to execute on a specific CPU for
> crash dump to work reliably. This can be due to firmware limitations,
> interrupt routing constraints, or platform-specific requirements where
> only a single CPU is able to safely enter the crash kernel.
>
> Add the panic_force_cpu= kernel command-line parameter to redirect panic
> execution to a designated CPU. When the parameter is provided, the CPU
> that initially triggers panic forwards the panic context to the target
> CPU via IPI, which then proceeds with the normal panic and kexec flow.
>
> The IPI delivery is implemented as a weak function (panic_smp_redirect_cpu)
> so architectures with NMI support can override it for more reliable delivery.
>
> If the specified CPU is invalid, offline, or a panic is already in
> progress on another CPU, the redirection is skipped and panic continues
> on the current CPU.
>
> Signed-off-by: Pnina Feder <pnina.feder@mobileye.com>
I can't see any obvious problem any longer ;-)
Feel free to use:
Reviewed-by: Petr Mladek <pmladek@suse.com>
Best Regards,
Petr
prev parent reply other threads:[~2026-01-29 16:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 10:24 [PATCH v8] panic: add panic_force_cpu= parameter to redirect panic to a specific CPU Pnina Feder
2026-01-22 19:08 ` kernel test robot
2026-01-23 1:08 ` kernel test robot
2026-01-23 2:11 ` kernel test robot
2026-01-24 1:14 ` Andrew Morton
2026-01-25 19:11 ` Pnina Feder
2026-01-26 12:26 ` [PATCH] panic: fix unused variable warning when SMP or CRASH_DUMP disabled Pnina Feder
2026-01-29 16:21 ` Petr Mladek [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=aXuIcrRvkhwITdWI@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=pnina.feder@mobileye.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=tglx@linutronix.de \
--cc=vkondra@mobileye.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 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.