[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87v86zt6qo.fsf@jogness.linutronix.de>
Date: Thu, 08 Feb 2024 14:45:43 +0106
From: John Ogness <john.ogness@...utronix.de>
To: Greg KH <gregkh@...uxfoundation.org>, Petr Mladek <pmladek@...e.com>
Cc: Sreenath Vijayan <sreenath.vijayan@...y.com>, corbet@....net,
jirislaby@...nel.org, rdunlap@...radead.org, rostedt@...dmis.org,
senozhatsky@...omium.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-serial@...r.kernel.org,
taichi.shimoyashiki@...y.com, daniel.palmer@...y.com,
anandakumar.balasubramaniam@...y.com
Subject: Re: [PATCH v4 2/2] tty/sysrq: Dump printk ring buffer messages via
sysrq
On 2024-02-08, Greg KH <gregkh@...uxfoundation.org> wrote:
> I just remembered all the rt-changes coming down the pipe for
> consoles/printk, is this going to mess with that?
It will not mess with the changes because we will continue to support
the legacy consoles anyway.
> So when this option fails when people need it the most, perhaps it's not
> worth adding? When else would people want to use it?
The feature could be massively improved once the rt-changes (atomic
consoles) become available.
Petr also brought up valid points about this feature (such as the
loglevel) that should be considered. We should clarify what exactly we
want this feature to do. The actual implementation is the easy part.
John
Powered by blists - more mailing lists