From: John Ogness <john.ogness@linutronix.de>
To: takakura@valinux.co.jp, pmladek@suse.com, rostedt@goodmis.org,
senozhatsky@chromium.org
Cc: linux-kernel@vger.kernel.org, Ryo Takakura <takakura@valinux.co.jp>
Subject: Re: [PATCH] printk: Allow direct printing for PREEMPT_RT during panic
Date: Thu, 10 Oct 2024 10:47:34 +0206 [thread overview]
Message-ID: <847cagmjsx.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <20241010035511.289657-1-takakura@valinux.co.jp>
On 2024-10-10, takakura@valinux.co.jp wrote:
> If PREEMPT_RT was enabled, printing for legacy consoles are deferred
> by default, including after printk_legacy_allow_panic_sync() during
> panic which allows direct printing afterwards in case of !PREEMPT_RT.
> As a result, printing of messages during panic for PREEMPT_RT
> is handled by the console_flush_on_panic() called at the end.
This is on purpose because legacy consoles are not safe in many contexts
under PREEMPT_RT. console_flush_on_panic() is used as a final "hope and
pray" excercise even though it is not safe on PREEMPT_RT, which is why
it is at the end of panic(). printk_legacy_allow_panic_sync() only
exists for !PREEMPT_RT.
> In case if kexec was loaded, console_flush_on_panic() will not be
> called and starts booting into the second kernel without printing
> the messages.
If legacy printing is allowed before, the kexec may never happen because
the unsafe legacy printers can hang the system.
> Allow direct printing for PREEMPT_RT during panic so that messages
> before kexec gets printed.
Sorry, NACK. This goes against everything we have worked for with the
rework. The solution is to update your console drivers to NBCON.
John Ogness
next prev parent reply other threads:[~2024-10-10 8:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 3:55 takakura
2024-10-10 8:41 ` John Ogness [this message]
2024-10-10 9:47 ` takakura
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=847cagmjsx.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=takakura@valinux.co.jp \
/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
Powered by JetHome