From: sashiko-bot@kernel.org
To: "John Ogness" <john.ogness@linutronix.de>,
"Petr Mladek" <pmladek@suse.com>
Cc: "Sergey Senozhatsky" <senozhatsky@chromium.org>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Ryan Roberts" <ryan.roberts@arm.com>,
"Breno Leitao" <leitao@debian.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Baoquan He" <baoquan.he@linux.dev>,
"Mike Rapoport" <rppt@kernel.org>,
"Pasha Tatashin" <pasha.tatashin@soleen.com>,
"Pratyush Yadav" <pratyush@kernel.org>,
"Dave Young" <ruirui.yang@linux.dev>,
kexec@lists.infradead.org
Subject: Re: [PATCH printk 5/6] printk: Add panic+kexec flush point
Date: Tue, 10 Nov 2026 12:31:44 +0000 [thread overview]
Message-ID: <sashiko-outbox-207026@kernel.org> (raw)
In-Reply-To: <20261109123127.489676-6-john.ogness@linutronix.de>
> During panic, nbcon consoles transition to atomic printing. However,
> there are consoles that do not support safe atomic printing
> (CON_NBCON_ATOMIC_UNSAFE). Such consoles will only flush during
> panic if their unsafe flush policy allows them to do so.
>
> The unsafe flush policy NBCON_PANIC_FLUSH only allows unsafe
> flushing when particular flushes are explicitly invoked. Call
> printk_trigger_flush(PR_FLUSH_RESTART) before performing the kexec
> in order to give such consoles a chance to perform an unsafe flush.
>
> Signed-off-by: John Ogness <john.ogness@linutronix.de>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261109123127.489676-1-john.ogness@linutronix.de?part=5
prev parent reply other threads:[~2026-11-10 12:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 12:31 [PATCH printk 0/6] Introduce policies for unsafe flushing John Ogness
2026-11-09 12:31 ` [PATCH printk 5/6] printk: Add panic+kexec flush point John Ogness
2026-11-10 12:31 ` sashiko-bot [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=sashiko-outbox-207026@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=baoquan.he@linux.dev \
--cc=john.ogness@linutronix.de \
--cc=kexec@lists.infradead.org \
--cc=leitao@debian.org \
--cc=pasha.tatashin@soleen.com \
--cc=pmladek@suse.com \
--cc=pratyush@kernel.org \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=ruirui.yang@linux.dev \
--cc=ryan.roberts@arm.com \
--cc=sashiko-reviews@lists.linux.dev \
--cc=senozhatsky@chromium.org \
/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