From: John Ogness <john.ogness@linutronix.de>
To: Carlos Bilbao <carlos.bilbao.osdev@gmail.com>,
carlos.bilbao@kernel.org, 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
Subject: Re: [PATCH v2 2/2] x86/panic: Add x86_panic_handler as default post-panic behavior
Date: Wed, 30 Apr 2025 10:04:05 +0206 [thread overview]
Message-ID: <84bjseozci.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <781ef1d7-f9c6-4a15-b94d-c735e83e7d01@gmail.com>
On 2025-04-29, Carlos Bilbao <carlos.bilbao.osdev@gmail.com> wrote:
>> I see no reason why you don't just use safe_halt() as your panic
>> handler.
>
> Yes, in my original implementation I simply used halt, but I was
> trying to be cautious in case any remaining messages hadn't flushed. I
> wonder, can we be certain that, as you said, all output (e.g., a
> backtrace) has already been displayed on screen at this point? I'm not
> sure.
Well, without this series, the kernel goes into an infinite loop. So if
the messages are not all out, they won't magically appear during the
infinite loop either.
John
next prev parent reply other threads:[~2025-04-30 7:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 21:59 [PATCH v2 0/2] panic: Reduce CPU consumption after panic carlos.bilbao
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 [this message]
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=84bjseozci.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=bilbao@vt.edu \
--cc=carlos.bilbao.osdev@gmail.com \
--cc=carlos.bilbao@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jan.glauber@gmail.com \
--cc=jani.nikula@intel.com \
--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 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.