From: Petr Mladek <pmladek@suse.com>
To: John Ogness <john.ogness@linutronix.de>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-fsdevel@vger.kernel.org, Jiri Slaby <jirislaby@kernel.org>,
linux-serial@vger.kernel.org
Subject: Re: [PATCH printk v6 00/17] add threaded printing + the rest
Date: Wed, 4 Sep 2024 16:30:50 +0200 [thread overview]
Message-ID: <ZthvGoJE26dOtsLm@pathway.suse.cz> (raw)
In-Reply-To: <20240904120536.115780-1-john.ogness@linutronix.de>
On Wed 2024-09-04 14:11:19, John Ogness wrote:
> Hi,
>
> This is v6 of a series to implement threaded console printing
> as well as some other minor pieces (such as proc and sysfs
> recognition of nbcon consoles). v5 is here [0].
>
> For information about the motivation of the nbcon consoles,
> please read the cover letter of the original v1 [1].
>
> This series provides the remaining pieces of the printk
> rework. All other components are either already mainline or are
> currently in linux-next. In particular this series does:
>
> - Implement dedicated printing threads per nbcon console.
>
> - Implement forced threading of legacy consoles for PREEMPT_RT.
>
> - Implement nbcon support for proc and sysfs console-related
> files.
>
> - Provide a new helper function nbcon_reacquire_nobuf() to
> allow nbcon console drivers to reacquire ownership.
>
> Note that this series does *not* provide an nbcon console
> driver. That will come in a follow-up series.
JFYI, the patchset has been committed into printk/linux.git,
branch rework/threaded-printk.
I am not completely sure if we add this early enough for 6.12.
On one hand, the patchset should not change the handling of legacy
consoles and it does not add any nbcon console. But it touches
many code paths where we decide how to flush the consoles
and could imagine doing "ugly" mistakes there.
OK, let's see how it works in linux-next in the following days.
There is still time to catch problems and make the decision.
Best Regards,
Petr
next prev parent reply other threads:[~2024-09-04 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 12:05 [PATCH printk v6 00/17] add threaded printing + the rest John Ogness
2024-09-04 12:05 ` [PATCH printk v6 12/17] proc: consoles: Add notation to c_start/c_stop John Ogness
2024-09-04 12:05 ` [PATCH printk v6 13/17] proc: Add nbcon support for /proc/consoles John Ogness
2024-09-04 14:30 ` Petr Mladek [this message]
2024-09-04 14:55 ` [PATCH printk v6 00/17] add threaded printing + the rest John Ogness
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=ZthvGoJE26dOtsLm@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--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;
as well as URLs for NNTP newsgroup(s).