[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200115215228.GH302770@tassilo.jf.intel.com>
Date: Wed, 15 Jan 2020 13:52:28 -0800
From: Andi Kleen <ak@...ux.intel.com>
To: Josh Poimboeuf <jpoimboe@...hat.com>
Cc: Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>,
Thomas Gleixner <tglx@...utronix.de>,
Borislav Petkov <bp@...en8.de>, Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
Tony Luck <tony.luck@...el.com>,
Michal Hocko <mhocko@...e.com>, linux-kernel@...r.kernel.org,
Neelima Krishnan <neelima.krishnan@...el.com>,
Dave Hansen <dave.hansen@...ux.intel.com>
Subject: Re: [PATCH] x86/cpu: Update cached HLE state on write to
TSX_CTRL_CPUID_CLEAR
On Wed, Jan 15, 2020 at 03:15:13PM -0600, Josh Poimboeuf wrote:
> On Fri, Jan 10, 2020 at 02:50:54PM -0800, Pawan Gupta wrote:
> > /proc/cpuinfo currently reports Hardware Lock Elision (HLE) feature to
> > be present on boot cpu even if it was disabled during the bootup. This
> > is because cpuinfo_x86->x86_capability HLE bit is not updated after TSX
> > state is changed via a new MSR IA32_TSX_CTRL.
> >
> > Update the cached HLE bit also since it is expected to change after an
> > update to CPUID_CLEAR bit in MSR IA32_TSX_CTRL.
> >
> > Signed-off-by: Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>
> > Tested-by: Neelima Krishnan <neelima.krishnan@...el.com>
> > Reviewed-by: Dave Hansen <dave.hansen@...ux.intel.com>
>
> From the Intel TAA deep dive page [1], it says:
>
> "On processors that enumerate IA32_ARCH_CAPABILITIES[TSX_CTRL] (bit
> 7)=1, HLE prefix hints are always ignored."
>
> So if the CPU has IA32_TSX_CTRL, HLE is implicitly disabled, so why
> would the HLE bit have been set in CPUID in the first place?
The CPUID is unchanged to avoid problems with software that checks
for unchanged CPUID. Unfortunately that exists in the wild.
-Andi
Powered by blists - more mailing lists