From: Dave Hansen <dave.hansen@intel.com>
To: Len Brown <lenb@kernel.org>,
peterz@infradead.org, tglx@linutronix.de, x86@kernel.org
Cc: rafael@kernel.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, Len Brown <len.brown@intel.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v3] x86/cpu: Add INTEL_LUNARLAKE_M to X86_BUG_MONITOR
Date: Wed, 20 Nov 2024 11:12:17 -0800 [thread overview]
Message-ID: <c5f9c185-11b1-4bc8-96be-a81895c2a096@intel.com> (raw)
In-Reply-To: <a4aa8842a3c3bfdb7fe9807710eef159cbf0e705.1731463305.git.len.brown@intel.com>
On 11/12/24 18:07, Len Brown wrote:
> From: Len Brown <len.brown@intel.com>
>
> Under some conditions, MONITOR wakeups on Lunar Lake processors
> can be lost, resulting in significant user-visible delays.
>
> Add LunarLake to X86_BUG_MONITOR so that wake_up_idle_cpu()
> always sends an IPI, avoiding this potential delay.
This kinda implies that X86_BUG_MONITOR only does one thing. What about
the two other places in the tree that check it. Are those relevant?
> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=219364
>
> Cc: stable@vger.kernel.org # 6.11
> Signed-off-by: Len Brown <len.brown@intel.com>
This obviously conflicts with the VFM infrastructure, but shouldn't this
also get backported to even older stable kernels?
I thought the "# 6.11" was to tell folks where it is *needed*, not where
it actually applies.
next prev parent reply other threads:[~2024-11-20 19:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 2:07 Len Brown
2024-11-13 9:05 ` Rafael J. Wysocki
2024-11-20 19:12 ` Dave Hansen [this message]
2024-11-20 20:08 ` Rafael J. Wysocki
2024-11-20 20:21 ` Dave Hansen
2024-11-21 10:22 ` Len Brown
2024-12-01 12:58 ` Thomas Gleixner
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=c5f9c185-11b1-4bc8-96be-a81895c2a096@intel.com \
--to=dave.hansen@intel.com \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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®