From: David Laight <David.Laight@ACULAB.COM>
To: 'Sebastian Andrzej Siewior' <bigeasy@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>,
John Ogness <john.ogness@linutronix.de>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Thomas Gleixner <tglx@linutronix.de>, Jan Kara <jack@suse.cz>,
Peter Zijlstra <peterz@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [GIT PULL] printk for 5.20
Date: Wed, 3 Aug 2022 14:46:08 +0000 [thread overview]
Message-ID: <45448fe59f7242fd90c5271a72ca937c@AcuMS.aculab.com> (raw)
In-Reply-To: <YuqHvu4zAzwq+BdZ@linutronix.de>
> On 2022-08-02 20:19:34 [-0700], Linus Torvalds wrote:
> > Seriously, even if you have strict RT requirements, you may also have
> > strict debugging requirements, and if something goes wrong, you want
> > to KNOW ABOUT IT. At that point, your RT rules may well fly out the
> > window, because you have more serious problems.
> >
> > End result: no way will I accept this kind of completely arbitrary and
> > frankly not very intelligent patch.
> >
> > If people want to disable console printing, that's THEIR CHOICE. It
> > could be a new config variable where you ASK people about what they
> > want. Not this kind of idiotic tying together of things.
There is already the sysctl kernel.printk
That can be used to limit the effects of console logging.
I don't actually remember the 'threaded console' stuff being
enabled/disabled in much the same way.
I end up setting '6 4 1 7' to avoid serial port delays.
But (in some sense) it might be useful to have the supressed
'info' messages output by a thread.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2022-08-03 14:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 15:07 [GIT PULL] printk for 5.20 Petr Mladek
2022-08-01 15:45 ` David Laight
2022-08-02 7:37 ` Petr Mladek
2022-08-03 3:19 ` Linus Torvalds
2022-08-03 14:35 ` Sebastian Andrzej Siewior
2022-08-03 14:46 ` David Laight [this message]
2022-08-03 15:43 ` Petr Mladek
2022-08-03 16:06 ` Steven Rostedt
2022-08-03 16:08 ` Linus Torvalds
2022-08-03 16:34 ` Sebastian Andrzej Siewior
2022-08-03 17:08 ` Ingo Molnar
2022-08-09 1:18 ` Thomas Gleixner
2022-08-11 13:38 ` Daniel Vetter
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=45448fe59f7242fd90c5271a72ca937c@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bigeasy@linutronix.de \
--cc=jack@suse.cz \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).