From: John Ogness <john.ogness@linutronix.de>
To: Petr Mladek <pmladek@suse.com>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>,
Andrew Murray <amurray@thegoodpenguin.co.uk>,
Chris Down <chris@chrisdown.name>,
linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-fsdevel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH printk 0/3] Introduce sync mode
Date: Fri, 10 Jul 2026 23:11:57 +0206 [thread overview]
Message-ID: <87cxwu4ksq.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <20260710144609.194487-1-john.ogness@linutronix.de>
On 2026-07-10, John Ogness <john.ogness@linutronix.de> wrote:
> As proposed in an LKML thread [0], here is a series to introduce a
> new console feature to use synchronous printing.
So the Sashiko review [0] found all kinds of issues and every one of
them are legitimate. In particular, I totally forgot about:
- the console_lock synchronization when boot consoles exist
- the various sites that _rely_ on kthreads printing when
printk_get_console_flush_type() reports ft.nbcon_offload
I will consider each of the points mentioned by Sashiko and include my
proposed solution in my response. I will need a few days to go through
all of it.
John
[0] https://sashiko.dev/#/patchset/20260710144609.194487-1-john.ogness%40linutronix.de
prev parent reply other threads:[~2026-07-10 21:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 14:45 [PATCH printk 0/3] Introduce sync mode John Ogness
2026-07-10 14:45 ` [PATCH printk 1/3] printk: Introduce console " John Ogness
2026-07-14 14:23 ` Petr Mladek
2026-07-10 14:45 ` [PATCH printk 2/3] proc: Add console sync support for /proc/consoles John Ogness
2026-07-14 15:03 ` Petr Mladek
2026-07-10 14:45 ` [PATCH printk 3/3] printk: Support setting console sync mode via console= John Ogness
2026-07-15 12:23 ` Petr Mladek
2026-07-10 21:05 ` John Ogness [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=87cxwu4ksq.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=amurray@thegoodpenguin.co.uk \
--cc=chris@chrisdown.name \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=skhan@linuxfoundation.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 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.