mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Petr Mladek <pmladek@suse.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	John Ogness <john.ogness@linutronix.de>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	Peter Zijlstra <peterz@infradead.org>,
	Petr Mladek <pmladek@suse.com>,
	linux-kernel@vger.kernel.org, Jon Hunter <jonathanh@nvidia.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Thierry Reding <thierry.reding@kernel.org>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: [GIT PULL] printk for 7.3-rc3
Date: Wed, 9 Sep 2026 11:08:43 +0200	[thread overview]
Message-ID: <aqEiG_01A3T0XhFW@pathway.suse.cz> (raw)

Hi Linus,

please pull some printk fixes from

  git://git.kernel.org/pub/scm/linux/kernel/git/printk/linux.git tags/printk-for-7.3-rc3

=======================================

- Use lazy irq_work for waking printk kthreads.

- Flush pending irq_work before destroying printk kthreads.

- Remove redundant WARN() when a printk kthread can't be created.

- Typo fix.

----------------------------------------------------------------

The primary motivation for making the irq_work lazy is that pending
IRQs block suspending and entering idle states on Tegra20 and Tegra30
platforms. They even did not boot after converting uart 8250 console
driver to the nbcon API.

It should be acceptable because printk kthreads are used for
non-emergency messages. They have to wait until they get
scheduled anyway.

This seems to be the least hacky solution which might even have
some positive effect in reducing the IRQ noise. And it allows
to keep the converted uart 8250 console driver in 7.3.

The discussion about the Tegra problems can be found at
https://lore.kernel.org/lkml/f3757a75-0ba1-4558-bf57-f19ab7e59a4c@nvidia.com/
https://lore.kernel.org/all/20260828155811.270462-1-john.ogness@linutronix.de/

----------------------------------------------------------------

Johan Hovold (1):
      console: fix /dev/kmsg reference in flags kernel doc

John Ogness (2):
      printk/nbcon: Flush nbcon_irq_work in nbcon_free()
      printk/nbcon: Change nbcon_irq_work to IRQ_WORK_LAZY

Petr Mladek (1):
      Merge branch 'for-7.4-trivial' into for-linus

Tetsuo Handa (1):
      printk: Don't WARN on kthread_run failure.

 include/linux/console.h | 2 +-
 kernel/printk/nbcon.c   | 6 ++++--
 kernel/printk/printk.c  | 2 +-
 3 files changed, 6 insertions(+), 4 deletions(-)

             reply	other threads:[~2026-09-09  9:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-09  9:08 Petr Mladek [this message]
2026-09-09 18:38 ` pr-tracker-bot

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=aqEiG_01A3T0XhFW@pathway.suse.cz \
    --to=pmladek@suse.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bigeasy@linutronix.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=john.ogness@linutronix.de \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=senozhatsky@chromium.org \
    --cc=thierry.reding@kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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®