[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251027161212.334219-1-john.ogness@linutronix.de>
Date: Mon, 27 Oct 2025 17:18:02 +0106
From: John Ogness <john.ogness@...utronix.de>
To: Petr Mladek <pmladek@...e.com>
Cc: Sergey Senozhatsky <senozhatsky@...omium.org>,
Steven Rostedt <rostedt@...dmis.org>,
Breno Leitao <leitao@...ian.org>,
Mike Galbraith <efault@....de>,
linux-kernel@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: [PATCH printk v2 0/1] allow unsafe write_atomic()
This is v2 of a series to allow unsafe write_atomic() console
callback implementations. This will allow console drivers to
move to the nbcon API, even if they are not capable of NMI-safe
atomic writing. The primary motivation for this series is to
support netconsole. v1 is here [0].
This version is based on the rework/nbcon-in-kdb branch of the
printk git in order to avoid conflicts due to the
console_is_usable() relocation.
The changes since v1:
- Use a global variable to track exactly when it is allowed to
flush using an unsafe write_atomic() rather than sprinkling
around similar checks based on states and code paths.
- Remove evil and incorrect WARN_ON() detection in
nbcon_emit_next_record().
John Ogness
[0] https://lore.kernel.org/lkml/20250912121852.2666874-1-john.ogness@linutronix.de
John Ogness (1):
printk: nbcon: Allow unsafe write_atomic() for panic
include/linux/console.h | 19 ++++++++++++++---
kernel/printk/nbcon.c | 45 ++++++++++++++++++++++++++++-------------
2 files changed, 47 insertions(+), 17 deletions(-)
base-commit: 62627bf0cadf6eae87d92fecf604c42160fe16ef
--
2.47.3
Powered by blists - more mailing lists