From: John Ogness <john.ogness@linutronix.de>
To: Petr Mladek <pmladek@suse.com>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org,
Jason Wessel <jason.wessel@windriver.com>,
Daniel Thompson <daniel.thompson@linaro.org>,
Douglas Anderson <dianders@chromium.org>,
Aaron Tomlin <atomlin@atomlin.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: [PATCH printk v3 0/7] various cleanups
Date: Mon, 17 Jul 2023 21:52:00 +0206 [thread overview]
Message-ID: <20230717194607.145135-1-john.ogness@linutronix.de> (raw)
Hi,
This is v3 of a series providing some cleanup in preparation
for the threaded/atomic console work. v2 is here [0]. This
series provides useful cleanups independent of the
threaded/atomic work.
Changes since v2:
- "NMI safety" patch split into 3 patches: console_unblank,
keep non-panic CPUs out, do not lock console on panic flush.
- console_unblank() aborts if there are no consoles implementing
an unblank() callback. This check is performed before taking
the console lock.
- Commit messages and comments updated to mention the details
discussed in the v2 feedback.
John Ogness
[0] https://lore.kernel.org/lkml/20230710134524.25232-1-john.ogness@linutronix.de
John Ogness (7):
kdb: Do not assume write() callback available
printk: Reduce console_unblank() usage in unsafe scenarios
printk: Keep non-panic-CPUs out of console lock
printk: Do not take console lock for console_flush_on_panic()
printk: Consolidate console deferred printing
printk: Add per-console suspended state
printk: Rename abandon_console_lock_in_panic() to other_cpu_in_panic()
include/linux/console.h | 3 +
kernel/debug/kdb/kdb_io.c | 2 +
kernel/printk/internal.h | 2 +
kernel/printk/printk.c | 213 +++++++++++++++++++++++++-----------
kernel/printk/printk_safe.c | 9 +-
5 files changed, 156 insertions(+), 73 deletions(-)
base-commit: 7ec85f3e089aa423a69559bf4555b6218b5a2ef7
--
2.30.2
next reply other threads:[~2023-07-17 19:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 19:46 John Ogness [this message]
2023-07-17 19:46 ` [PATCH printk v3 1/7] kdb: Do not assume write() callback available John Ogness
2023-07-17 19:46 ` [PATCH printk v3 2/7] printk: Reduce console_unblank() usage in unsafe scenarios John Ogness
2023-07-18 3:39 ` Sergey Senozhatsky
2023-07-18 10:21 ` Petr Mladek
2023-07-17 19:46 ` [PATCH printk v3 3/7] printk: Keep non-panic-CPUs out of console lock John Ogness
2023-07-18 3:17 ` Sergey Senozhatsky
2023-07-18 10:23 ` Petr Mladek
2023-07-17 19:46 ` [PATCH printk v3 4/7] printk: Do not take console lock for console_flush_on_panic() John Ogness
2023-07-18 3:18 ` Sergey Senozhatsky
2023-07-18 10:28 ` Petr Mladek
2023-07-17 19:46 ` [PATCH printk v3 5/7] printk: Consolidate console deferred printing John Ogness
2023-07-17 19:46 ` [PATCH printk v3 6/7] printk: Add per-console suspended state John Ogness
2023-07-17 19:46 ` [PATCH printk v3 7/7] printk: Rename abandon_console_lock_in_panic() to other_cpu_in_panic() John Ogness
2023-07-18 10:44 ` [PATCH printk v3 0/7] various cleanups Petr Mladek
2023-07-21 9:17 ` Petr Mladek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230717194607.145135-1-john.ogness@linutronix.de \
--to=john.ogness@linutronix.de \
--cc=atomlin@atomlin.com \
--cc=daniel.thompson@linaro.org \
--cc=dianders@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=jason.wessel@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®