Messages in this thread | | | From | John Ogness <> | Subject | Re: [BUG] Threaded printk breaks early debugging | Date | Mon, 13 Jun 2022 01:08:23 +0206 |
| |
On 2022-06-12, Sergey Senozhatsky <senozhatsky@chromium.org> wrote: > Should a situation when we have only one online CPU be enough of a > reason to do direct printing? Otherwise we might not have CPUs to > wakeup khtread on, e.g. when CPU that printk is in atomic section for > too long.
IMHO, no. Especially in that situation, we do not want printk causing that atomic section to become even longer. If the machine has entered normal operation, we want printk out of the way.
John Ogness
| |