From: John Ogness <john.ogness@linutronix.de>
To: Greg KH <gregkh@linuxfoundation.org>, Petr Mladek <pmladek@suse.com>
Cc: Sreenath Vijayan <sreenath.vijayan@sony.com>,
corbet@lwn.net, jirislaby@kernel.org, rdunlap@infradead.org,
rostedt@goodmis.org, senozhatsky@chromium.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org, taichi.shimoyashiki@sony.com,
daniel.palmer@sony.com, anandakumar.balasubramaniam@sony.com
Subject: Re: [PATCH v4 2/2] tty/sysrq: Dump printk ring buffer messages via sysrq
Date: Thu, 08 Feb 2024 14:45:43 +0106 [thread overview]
Message-ID: <87v86zt6qo.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <2024020845-antiquely-faculty-407d@gregkh>
On 2024-02-08, Greg KH <gregkh@linuxfoundation.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
next prev parent reply other threads:[~2024-02-08 13:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 10:16 [PATCH v4 0/2] Add support to dump printk buffer to console " Sreenath Vijayan
2024-02-01 10:23 ` [PATCH v4 1/2] printk: Add function to dump printk buffer directly to consoles Sreenath Vijayan
2024-02-01 11:28 ` John Ogness
2024-02-07 14:43 ` Petr Mladek
2024-02-14 10:33 ` Sreenath Vijayan
2024-02-01 10:29 ` [PATCH v4 2/2] tty/sysrq: Dump printk ring buffer messages via sysrq Sreenath Vijayan
2024-02-01 11:29 ` John Ogness
2024-02-07 15:09 ` Petr Mladek
2024-02-08 10:18 ` Greg KH
2024-02-08 13:39 ` John Ogness [this message]
2024-02-14 10:40 ` Sreenath Vijayan
2024-02-14 11:12 ` Sreenath Vijayan
2024-02-26 8:01 ` Sreenath Vijayan
2024-02-26 9:28 ` John Ogness
2024-02-07 14:12 ` [PATCH v4 0/2] Add support to dump printk buffer to console " Petr Mladek
2024-02-14 10:30 ` Sreenath Vijayan
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=87v86zt6qo.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=anandakumar.balasubramaniam@sony.com \
--cc=corbet@lwn.net \
--cc=daniel.palmer@sony.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=sreenath.vijayan@sony.com \
--cc=taichi.shimoyashiki@sony.com \
/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
all inboxes | Powered by JetHome®