From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: John Ogness <john.ogness@linutronix.de>
Cc: "Jiri Slaby" <jirislaby@kernel.org>,
"Andy Shevchenko" <andy.shevchenko@gmail.com>,
"Petr Mladek" <pmladek@suse.com>,
"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
"Jon Hunter" <jonathanh@nvidia.com>,
"Thierry Reding" <thierry.reding@kernel.org>,
linux-kernel@vger.kernel.org,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Crescent Hsieh" <crescentcy.hsieh@moxa.com>,
"Hugo Villeneuve" <hvilleneuve@dimonoff.com>,
linux-serial@vger.kernel.org
Subject: Re: [PATCH tty 0/1] Make 8250 deferred MSR handling LAZY
Date: Mon, 21 Sep 2026 14:15:57 +0200 [thread overview]
Message-ID: <2026092133-runt-sharper-445c@gregkh> (raw)
In-Reply-To: <87ld8usz1x.fsf@jogness.linutronix.de>
On Mon, Sep 21, 2026 at 12:07:46PM +0206, John Ogness wrote:
> Hi Greg, Jiri,
>
> On 2026-08-28, John Ogness <john.ogness@linutronix.de> wrote:
> > There was a report and follow-up discussion [0] about a problem
> > using regular irq_work queuing on some platforms when entering
> > cpuidle. To circumvent this problem, all irq_work for printk will
> > become IRQ_WORK_LAZY [1].
> >
> > The 8250 console driver uses irq_work to defer MSR handling during
> > atomic printing. This means it is vulnerable to the same problem if,
> > for example, a WARN() is hit while entering cpuidle on one of the
> > affected platforms.
> >
> > Avoid the problem for deferred MSR handling by changing
> > console_msr_work to IRQ_WORK_LAZY.
>
> Any chance of getting this into 7.3? A similar patch went into 7.3-rc3
> for printk:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/kernel/printk?id=560f4deda32785e260056200f8bb911c475c5b88
>
> Or do I need to send a v2 with an updated commit message? I could
> rephrase it similar to the related printk commit. Something like this:
>
> Change console_msr_work (defers MSR handling) to be IRQ_WORK_LAZY,
> thus not raising an IRQ upon irq_work queuing. The irq_work is then
> handled on the next kernel tick. This additional delay is acceptable
> because the MSR handling also occurs in the an interrupt handler, if
> mctrl is queried, and during console resume. Using IRQ_WORK_LAZY has
> the benefit of not needing to raise an IRQ for each line of atomic
> console printing when modem control is active.
>
> On a side note, the Tegra20 and Tegra30 platforms can hang if an
> irq_work IRQ is raised while entering cpuidle states. This problem
> was reproducible by performing atomic printing while entering cpuidle.
> So this change also provides a workaround for these platforms (as
> long as they are not running tickless).
An updated changelog would be great, then I can take it for 7.3-final
easier.
thanks,
greg k-h
prev parent reply other threads:[~2026-09-21 12:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 15:58 John Ogness
2026-08-28 15:58 ` [PATCH tty 1/1] serial: 8250: Change console_msr_work to IRQ_WORK_LAZY John Ogness
2026-08-28 16:06 ` Sebastian Andrzej Siewior
2026-08-28 16:41 ` John Ogness
2026-08-28 17:06 ` Jon Hunter
2026-08-30 7:42 ` Andy Shevchenko
2026-08-31 8:20 ` Sebastian Andrzej Siewior
2026-09-01 9:20 ` Jon Hunter
2026-08-31 15:23 ` Petr Mladek
2026-09-01 7:50 ` Sebastian Andrzej Siewior
2026-09-02 8:34 ` Jon Hunter
2026-09-21 10:01 ` [PATCH tty 0/1] Make 8250 deferred MSR handling LAZY John Ogness
2026-09-21 12:15 ` Greg Kroah-Hartman [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=2026092133-runt-sharper-445c@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=crescentcy.hsieh@moxa.com \
--cc=hvilleneuve@dimonoff.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=pmladek@suse.com \
--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 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®