lkml.org 
[lkml]   [2022]   [Aug]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRE: [GIT PULL] printk for 5.20
Date
> 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)
\
 
 \ /
  Last update: 2022-08-03 16:46    [W:0.102 / U:2.208 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site