From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Dave Hansen <dave.hansen@intel.com>, LKML <linux-kernel@vger.kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: x86/idle: Remove barriers for X86_BUG_CLFLUSH_MONITOR
Date: Wed, 2 Apr 2025 15:04:16 +0100 [thread overview]
Message-ID: <c49c5573-893a-4352-8437-d2d9b7af5327@citrix.com> (raw)
In-Reply-To: <eeca95c5-5724-4205-8449-644d91eafd48@intel.com>
On 02/04/2025 3:01 pm, Dave Hansen wrote:
> On 4/2/25 02:10, Andrew Cooper wrote:
>> i.e. The SDM was incorrect at the time, and barriers should not have been
>> inserted. Double checking the original AAI65 errata (not available from
>> intel.com any more) shows no mention of barriers either.
> There's a near copy-and-paste of that code here:
>
>> static __cpuidle void mwait_idle(void)
>> {
>> if (!current_set_polling_and_test()) {
>> if (this_cpu_has(X86_BUG_CLFLUSH_MONITOR)) {
>> mb(); /* quirk */
>> clflush((void *)¤t_thread_info()->flags);
>> mb(); /* quirk */
>> }
> Any reason it can't get the same treatment?
Oh, yes that should get the same treatment. (Sorry, too may cross-ports
between Xen and Linux trying to untangle this mess).
I'll submit a v2.
~Andrew
prev parent reply other threads:[~2025-04-02 14:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 9:10 Andrew Cooper
2025-04-02 9:53 ` Borislav Petkov
2025-04-02 10:10 ` [tip: x86/mm] x86/idle: Remove mb() barriers for X86_BUG_CLFLUSH_MONITOR in mwait_idle_with_hints() tip-bot2 for Andrew Cooper
2025-04-02 10:17 ` Andrew Cooper
2025-04-02 14:01 ` x86/idle: Remove barriers for X86_BUG_CLFLUSH_MONITOR Dave Hansen
2025-04-02 14:04 ` Andrew Cooper [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=c49c5573-893a-4352-8437-d2d9b7af5327@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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®