From: Peter Zijlstra <peterz@infradead.org>
To: Pnina Feder <PNINA.FEDER@mobileye.com>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"pmladek@suse.com" <pmladek@suse.com>,
"bhe@redhat.com" <bhe@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"lkp@intel.com" <lkp@intel.com>,
"mgorman@suse.de" <mgorman@suse.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"senozhatsky@chromium.org" <senozhatsky@chromium.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
Vladimir Kondratiev <Vladimir.Kondratiev@mobileye.com>
Subject: Re: [PATCH v4] panic: add panic_force_cpu= parameter to redirect panic to a specific CPU
Date: Mon, 12 Jan 2026 08:49:10 +0100 [thread overview]
Message-ID: <20260112074910.GC830755@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <MRWPR09MB80226D4647723C15D4FEC0608F85A@MRWPR09MB8022.eurprd09.prod.outlook.com>
On Thu, Jan 08, 2026 at 08:09:33PM +0000, Pnina Feder wrote:
> > Also, if this is a 'requirement' for kexec or the like, this
> > shouldn't be a command line argument, but something that's set-up by
> > kexec itself for functional reasons.
>
> Since the redirection needs to happen before other CPUs are stopped,
> would a sysctl be preferable? The user could set it when loading the
> crash kernel.
I was more thinking about platform setup, it would set this on boot, and
equally dis-allow hot-unplug of the magical CPU.
next prev parent reply other threads:[~2026-01-12 7:49 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-01 12:32 [PATCH] panic/kexec: Allow forcing panic execution on a specific CPU Pnina Feder
2026-01-03 18:29 ` Andrew Morton
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 [this message]
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=20260112074910.GC830755@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=PNINA.FEDER@mobileye.com \
--cc=Vladimir.Kondratiev@mobileye.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=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=tglx@linutronix.de \
/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