[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <c49c5573-893a-4352-8437-d2d9b7af5327@citrix.com>
Date: Wed, 2 Apr 2025 15:04:16 +0100
From: Andrew Cooper <andrew.cooper3@...rix.com>
To: Dave Hansen <dave.hansen@...el.com>, LKML <linux-kernel@...r.kernel.org>
Cc: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
Borislav Petkov <bp@...en8.de>, Dave Hansen <dave.hansen@...ux.intel.com>,
x86@...nel.org, "H. Peter Anvin" <hpa@...or.com>
Subject: Re: x86/idle: Remove barriers for X86_BUG_CLFLUSH_MONITOR
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
Powered by blists - more mailing lists