On (09/18/19 09:42), John Ogness wrote: > > It's going to be a bit harder when we have per-console kthread. > > Each console has its own iterator. This iterators will need to advance, > regardless if the message was printed via write() or write_atomic().
Great.
->atomic_write() path will make sure that kthread is parked or will
those compete for uart port?
-ss
