From: carlos.bilbao@kernel.org
To: tglx@linutronix.de, seanjc@google.com, jan.glauber@gmail.com
Cc: bilbao@vt.edu, pmladek@suse.com, akpm@linux-foundation.org,
jani.nikula@intel.com, linux-kernel@vger.kernel.org,
gregkh@linuxfoundation.org, takakura@valinux.co.jp,
john.ogness@linutronix.de,
Carlos Bilbao <carlos.bilbao@kernel.org>
Subject: [PATCH v2 0/2] panic: Reduce CPU consumption after panic
Date: Mon, 28 Apr 2025 16:59:50 -0500 [thread overview]
Message-ID: <20250428215952.1332985-1-carlos.bilbao@kernel.org> (raw)
From: Carlos Bilbao <carlos.bilbao@kernel.org>
Provide a priority-based mechanism to set the behavior of the kernel at
the post-panic stage -- the current default is a waste of CPU except for
cases with console that generate insightful output.
In v1 [1], I illustrated the potential to reduce unnecessary CPU usage
with an experiment with VMs. The main delta is that, instead of a weak
function that archs can overwrite, we provide a flexible priority-based
mechanism (following suggestions by Sean Christopherson),
panic_set_handling().
[1] https://lore.kernel.org/all/20250326151204.67898-1-carlos.bilbao@kernel.org/
Carlos:
panic: Allow for dynamic custom behavior after panic
x86/panic: Add x86_panic_handler as default post-panic behavior
---
arch/x86/kernel/setup.c | 12 ++++++++++++
include/linux/panic.h | 2 ++
kernel/panic.c | 27 +++++++++++++++++++++++++++
3 files changed, 41 insertions(+)
next reply other threads:[~2025-04-28 23:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 21:59 carlos.bilbao [this message]
2025-04-28 21:59 ` [PATCH v2 1/2] panic: Allow for dynamic custom behavior " carlos.bilbao
2025-04-29 14:54 ` Sean Christopherson
2025-04-29 14:25 ` Carlos Bilbao
2025-04-28 21:59 ` [PATCH v2 2/2] x86/panic: Add x86_panic_handler as default post-panic behavior carlos.bilbao
2025-04-29 14:57 ` Sean Christopherson
2025-04-29 14:25 ` Carlos Bilbao
2025-04-29 16:53 ` John Ogness
2025-04-29 15:25 ` Carlos Bilbao
2025-04-30 7:58 ` John Ogness
2025-05-07 19:56 ` Carlos Bilbao
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=20250428215952.1332985-1-carlos.bilbao@kernel.org \
--to=carlos.bilbao@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bilbao@vt.edu \
--cc=gregkh@linuxfoundation.org \
--cc=jan.glauber@gmail.com \
--cc=jani.nikula@intel.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=seanjc@google.com \
--cc=takakura@valinux.co.jp \
--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
all inboxes | Powered by JetHome®