[PATCH printk v4 3/6] printk: remove safe buffers

Petr Mladek pmladek at suse.com
Wed Jul 21 04:25:47 PDT 2021

On Thu 2021-07-15 21:39:56, John Ogness wrote:
> With @logbuf_lock removed, the high level printk functions for
> storing messages are lockless. Messages can be stored from any
> context, so there is no need for the NMI and safe buffers anymore.
> Remove the NMI and safe buffers.
> Although the safe buffers are removed, the NMI and safe context
> tracking is still in place. In these contexts, store the message
> immediately but still use irq_work to defer the console printing.
> Since printk recursion tracking is in place, safe context tracking
> for most of printk is not needed. Remove it. Only safe context
> tracking relating to the console and console_owner locks is left
> in place. This is because the console and console_owner locks are
> needed for the actual printing.
> Signed-off-by: John Ogness <john.ogness at linutronix.de>

Reviewed-by: Petr Mladek <pmladek at suse.com>

Best Regards,

More information about the kexec mailing list