On (20/09/23 17:08), Prasad Sodagudi wrote: > From: Mohammed Khajapasha <mkh...@codeaurora.org> > > The thread which initiates the hot plug can get scheduled > out, while trying to acquire the console lock, > thus increasing the hot plug latency. This option > allows to selectively disable the console flush and > in turn reduce the hot plug latency.
It can schedule out or get preempted pretty much anywhere at any
time. printk->console_lock is not special in this regard. What am
I missing?
-ss
