From: John Ogness <john.ogness@linutronix.de>
To: Petr Mladek <pmladek@suse.com>, Chris Down <chris@chrisdown.name>
Cc: linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
kernel-team@fb.com
Subject: Re: design: was: Re: [RFC PATCH v2] printk: console: Allow each console to have its own loglevel
Date: Fri, 08 Jul 2022 21:10:35 +0206 [thread overview]
Message-ID: <87o7xz5su4.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <YshL2M8VdIEONDdc@alley>
On 2022-07-08, Petr Mladek <pmladek@suse.com> wrote:
> The console-specific loglevel might be set by:
>
> + "console=device,options/loglevel" kernel parameter at boot time
I ask if we avoid the use of "/loglevel" and instead use a generic
scheme of:
console=device,option,option,option
Of course, it would mean that the type of option would need to be
specified. Something like:
console=ttyS0,115200n8,loglevel=3
The reason why I make such a request is because I would like to be able
to support disabling threading for certain consoles. Something like:
console=ttyS0,115200n8,nothread
or when we have atomic consoles that we can specify that they are always
used with a "sync" option:
console=ttyS0,115200n8,sync
This is not the time to discuss what those strings should be. The point
is that we should use a syntax that allows adding more options for the
future.
Linus already [0] showed some approval to this method of option
extending as I suggested the "mute" option to have consoles keep quiet.
John Ogness
P.S. FWIW, I think this is a nice feature. I even mentioned it in my
LPC2019 printk talk, as there were previous efforts [1] to get this
feature implemented.
[0] https://lore.kernel.org/lkml/CAHk-=wif0QueN8ovkm_x7TsOgOHjRrOa4wU-zHgBP=FTAnzvNA@mail.gmail.com
[1] https://lore.kernel.org/lkml/bc1fe800930be76761b2bb4e6108fe5876a005c9.1491345440.git.calvinowens@fb.com
next prev parent reply other threads:[~2022-07-08 19:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 12:57 [RFC PATCH v2] printk: console: Allow each console to have its own loglevel Chris Down
2022-05-20 16:06 ` Rik van Riel
2022-07-07 14:38 ` Petr Mladek
2022-07-13 14:32 ` Chris Down
2022-05-21 18:51 ` Greg Kroah-Hartman
2022-05-21 19:23 ` Chris Down
2022-05-23 13:09 ` Vincent Whitchurch
2022-05-23 14:24 ` Chris Down
2022-06-16 15:57 ` Chris Down
2022-07-08 15:23 ` design: was: " Petr Mladek
2022-07-08 19:04 ` John Ogness [this message]
2022-07-11 8:32 ` Petr Mladek
2022-07-11 10:17 ` Sergey Senozhatsky
2022-07-13 14:50 ` Chris Down
2022-07-13 14:49 ` Chris Down
2022-07-14 15:44 ` Petr Mladek
2022-07-15 12:49 ` Petr Mladek
2022-07-15 13:00 ` Chris Down
2022-07-19 12:11 ` Chris Down
2022-07-19 13:00 ` Petr Mladek
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=87o7xz5su4.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=chris@chrisdown.name \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
/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