On Wed, 18 Sep 2019 10:25:46 +0900 Sergey Senozhatsky <sergey.senozhatsky.w...@gmail.com> wrote:
> On (09/13/19 15:26), John Ogness wrote: > > 2. A kernel thread will be created for each registered console, each > > responsible for being the sole printers to their respective > > consoles. With this, console printing is _fully_ decoupled from printk() > > callers. > > sysrq over serial? > > What we currently have is hacky, but, as usual, is a "best effort": > > >> serial driver IRQ > > serial_handle_irq() [console driver] > uart_handle_sysrq_char() > handle_sysrq() > printk() > call_console_drivers() > serial_write() [re-enter console driver] > > offloading this to kthread may be unreliable. But we also talked about an "emergency flush" which will not wait for the kthreads to finish and just output everything it can find in the printk buffers (expecting that the consoles have an "emergency" handler. We can add a sysrq to do an emergency flush. -- Steve
