[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZsS0efABGgFmXBwB@pathway.suse.cz>
Date: Tue, 20 Aug 2024 17:21:29 +0200
From: Petr Mladek <pmladek@...e.com>
To: John Ogness <john.ogness@...utronix.de>
Cc: Sergey Senozhatsky <senozhatsky@...omium.org>,
Steven Rostedt <rostedt@...dmis.org>,
Thomas Gleixner <tglx@...utronix.de>, linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Jani Nikula <jani.nikula@...el.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Ryo Takakura <takakura@...inux.co.jp>,
Joel Granados <j.granados@...sung.com>,
Lukas Wunner <lukas@...ner.de>, Uros Bizjak <ubizjak@...il.com>
Subject: Re: [PATCH printk v8 29/35] printk: Coordinate direct printing in
panic
On Tue 2024-08-20 08:35:55, John Ogness wrote:
> If legacy and nbcon consoles are registered and the nbcon
> consoles are allowed to flush (i.e. no boot consoles
> registered), the legacy consoles will no longer perform
> direct printing on the panic CPU until after the backtrace
> has been stored. This will give the safe nbcon consoles a
> chance to print the panic messages before allowing the
> unsafe legacy consoles to print.
>
> If no nbcon consoles are registered or they are not allowed
> to flush because boot consoles are registered, there is no
> change in behavior (i.e. legacy consoles will always attempt
> to print from the printk() caller context).
>
> Signed-off-by: John Ogness <john.ogness@...utronix.de>
Reviewed-by: Petr Mladek <pmladek@...e.com>
Best Regards,
Petr
Powered by blists - more mailing lists