From: "Adamski, Krzysztof (Nokia - PL/Wroclaw)" <krzysztof.adamski@nokia.com>
To: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
Cc: Vincent Whitchurch <vincent.whitchurch@axis.com>,
Greg KH <gregkh@linuxfoundation.org>,
"jslaby@suse.com" <jslaby@suse.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tty: Add NULL TTY driver
Date: Fri, 12 Apr 2019 07:34:02 +0000 [thread overview]
Message-ID: <20190412073344.GA28707@localhost.localdomain> (raw)
In-Reply-To: <c77474fd-96d6-392b-9a54-fd7e6a29b72d@metux.net>
On Fri, Apr 12, 2019 at 09:17:28AM +0200, Enrico Weigelt, metux IT consult wrote:
>On 11.04.19 15:05, Adamski, Krzysztof (Nokia - PL/Wroclaw) wrote:
>
>> There are (embedded) cases where the kernel ring buffer is stored for> log inspection and all the logs that are *not* wanted there (like>
>interactive debug logs, some progress bar, etc) are send specifically
>to> /dev/console to avoid sending them to normal log store (as they are
>only> useful when debugging over console). In non-debug mode
>/dev/console> becomes /dev/null to speed things up.
>So, in your case, it doesn't need to be an actual tty, any file/chardev
>already do it, correct ? But then, why is that new driver needed ?
>
Well, that depends. If the program doing those writes expects /dev/console
to be a tty device, then it cannot be any file. But, yes, there are usually
other ways of achieving this goal that do not involve adding kernel driver
but none of them is as convenient as having this kernel support. With this,
we can only switch kernel cmdline without any modifications to the rootfs.
The discussed kernel driver is very simple so there is little effort required
for this convenience. Maintaining it would be very easy and, of course,
anybody not needing it, can simply disable it in config so there is no cost.
Krzysztof
next prev parent reply other threads:[~2019-04-12 7:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 11:33 [PATCH] tty: Add NULL TTY driver Vincent Whitchurch
2019-04-03 13:12 ` Greg KH
2019-04-03 14:11 ` Vincent Whitchurch
2019-04-05 8:39 ` Enrico Weigelt, metux IT consult
2019-04-05 9:00 ` Vincent Whitchurch
2019-04-05 12:32 ` Enrico Weigelt, metux IT consult
2019-04-11 13:05 ` Adamski, Krzysztof (Nokia - PL/Wroclaw)
2019-04-12 7:17 ` Enrico Weigelt, metux IT consult
2019-04-12 7:34 ` Adamski, Krzysztof (Nokia - PL/Wroclaw) [this message]
[not found] ` <0a50343e-6ebe-f725-82f7-5c127b5ce2e6@nokia.com>
2019-04-12 11:40 ` Enrico Weigelt, metux IT consult
2019-04-12 13:12 ` Adamski, Krzysztof (Nokia - PL/Wroclaw)
2019-04-11 15:28 ` Vincent Whitchurch
2019-04-12 11:31 ` Enrico Weigelt, metux IT consult
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=20190412073344.GA28707@localhost.localdomain \
--to=krzysztof.adamski@nokia.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@metux.net \
--cc=vincent.whitchurch@axis.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