Messages in this thread | | | Date | Sat, 18 Jun 2022 17:30:44 -0700 | Subject | Re: [PATCH] printk: allow direct console printing to be enabled always | From | Randy Dunlap <> |
| |
On 6/17/22 06:38, Jason A. Donenfeld wrote: > diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt > index 8090130b544b..a960c47a2002 100644 > --- a/Documentation/admin-guide/kernel-parameters.txt > +++ b/Documentation/admin-guide/kernel-parameters.txt > @@ -4389,6 +4389,14 @@ > printk.time= Show timing data prefixed to each printk message line > Format: <bool> (1/Y/y=enable, 0/N/n=disable) > > + printk.always_direct= > + Rather than using kthreads for printk output, always > + write to the console immediately. This has performance > + implications, but will result in a more faithful > + ordering and interleaving with other processes writing > + to the console. > + Format: <bool> (1/Y/y=enable, 0/N/n=disable)
or:
+ Format: <bool> (1/Y/y/T/t/on=enable, 0/N/n/F/f/off=disable)
-- ~Randy
| |