Messages in this thread | | | Date | Fri, 29 Sep 2017 01:02:30 +0900 | From | Sergey Senozhatsky <> | Subject | Re: [PATCH 0/3] printk: Add force_early_printk boot param |
| |
On (09/28/17 14:18), Peter Zijlstra wrote: > Most all printk() bits are terminally broken because they rely on the scheduler > and blocking locks to function, making them unsuitable for debugging the > scheduler and NMI context things.
hold on... wait a second... the scheduler is not lockless yet? darn...
ok, I think having something like that in printk.c wouldn't hurt. Petr was going to take a look, IIRC.
but what's up with that scheduler thing I keep hearing about, must be something new, can I disable it in kconfig? it seems to be conflicting with CONFIG_PRINTK.
-ss
| |