public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Thu, 11 Apr 2019 13:05:20 +0000	[thread overview]
Message-ID: <20190411130458.GA11390@localhost.localdomain> (raw)
In-Reply-To: <de23cde3-c77f-cdbf-0968-d7f44c723120@metux.net>

On Fri, Apr 05, 2019 at 02:32:41PM +0200, Enrico Weigelt, metux IT consult wrote:
>On 05.04.19 11:00, Vincent Whitchurch wrote:
>> On Fri, Apr 05, 2019 at 10:39:43AM +0200, Enrico Weigelt, metux IT consult wrote:
>>> On 03.04.19 16:11, Vincent Whitchurch wrote:
>>>
>>>> Especially on embedded systems, it would be convenient to have a simple
>>>> way to disable the console (both for kernel and userspace) on a system
>>>> which normally uses it, to free up the UART for other things.
>>>
>>> Just symlinking to /dev/null does not work ?
>>
>> No, /dev/null does not support the TTY ioctls.
>
>hmm, wo (which programs) do you need, that really need them ?
>
>>> OTOH, if you're introducing a dummy console, wouldn't a ringbuffer that,
>>> can be read out later, a better option ?
>>
>> There is already a ttyprintk driver in mainline to send these messages
>> to the printk ring buffer if one is actually intrested in what is
>> written to the console.  There's no option to enable it via console= in
>> mainline but I have a patch for that too.
>
>Great. IMHO, that would be the better way.

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.

I would personally benefit from Vincents patch. In fact I found this
thread because I was considering doing exactly the same for our system.

Krzysztof

  reply	other threads:[~2019-04-11 13:05 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) [this message]
2019-04-12  7:17             ` Enrico Weigelt, metux IT consult
2019-04-12  7:34               ` Adamski, Krzysztof (Nokia - PL/Wroclaw)
     [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=20190411130458.GA11390@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