From: Petr Mladek <pmladek@suse.com>
To: John Ogness <john.ogness@linutronix.de>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Jon Hunter <jonathanh@nvidia.com>,
Thierry Reding <thierry.reding@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, Thomas Gleixner <tglx@kernel.org>
Subject: Re: [PATCH printk v3 0/2] nbcon irq_work fixes
Date: Wed, 2 Sep 2026 12:02:00 +0200 [thread overview]
Message-ID: <apf0GKgd5vxBAkOl@pathway.suse.cz> (raw)
In-Reply-To: <20260901093245.344455-1-john.ogness@linutronix.de>
On Tue 2026-09-01 11:37:41, John Ogness wrote:
> Hi,
>
> This is v3 of a series to address some irq_work issues with nbcon.
> Initially motivated as a workaround for hardware-related regressions
> reported [0], it turns out that the workaround is actually a nice
> improvement for nbcon deferred printing in general.
>
> v2 is here [1].
>
> The changes since v2:
>
> - On nbcon_free(), perform the irq_work flush before stopping the
> kthread printer.
>
> - Rework the commit message of patch 2/2 so that reducing interrupts
> is the primary motivation and the Tegra workaround is a secondary
> "benefit". I really want the Tegra workaround information to stay
> in the commit message because it is historically significant.
>
> John Ogness
>
> [0] https://lore.kernel.org/lkml/f3757a75-0ba1-4558-bf57-f19ab7e59a4c@nvidia.com
> [1] https://lore.kernel.org/lkml/20260828140218.232439-1-john.ogness@linutronix.de
>
> John Ogness (2):
> printk/nbcon: Flush nbcon_irq_work in nbcon_free()
> printk/nbcon: Change nbcon_irq_work to IRQ_WORK_LAZY
>
> kernel/printk/nbcon.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
JFYI, the patchset has been comitted into printk/linux.git,
branch for-7.3-irq-work-fixes.
I am going to give it few days in linux-next. Then I will create
a pull request for 7.3 unless any problems got reported.
Best Regards,
Petr
prev parent reply other threads:[~2026-09-02 10:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 9:31 [PATCH printk v3 0/2] nbcon irq_work fixes John Ogness
2026-09-01 9:31 ` [PATCH printk v3 1/2] printk/nbcon: Flush nbcon_irq_work in nbcon_free() John Ogness
2026-09-02 9:06 ` Petr Mladek
2026-09-01 9:31 ` [PATCH printk v3 2/2] printk/nbcon: Change nbcon_irq_work to IRQ_WORK_LAZY John Ogness
2026-09-01 9:53 ` John Ogness
2026-09-02 10:02 ` Petr Mladek [this message]
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=apf0GKgd5vxBAkOl@pathway.suse.cz \
--to=pmladek@suse.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=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=tglx@kernel.org \
--cc=thierry.reding@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.