diff options
author | Dave Hansen <dave.hansen@linux.intel.com> | 2023-05-16 12:24:25 -0700 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2023-05-30 12:42:14 +0100 |
commit | 4d19f7698681c59b4c1f25dc343a025d91cc4827 (patch) | |
tree | 63d38735e1c09af6213373bbfa58c37e16f3d640 /tools | |
parent | 87d2eeb4b5052467e5865efc91a315163ea83f9c (diff) | |
download | linux-stable-4d19f7698681c59b4c1f25dc343a025d91cc4827.tar.gz linux-stable-4d19f7698681c59b4c1f25dc343a025d91cc4827.tar.bz2 linux-stable-4d19f7698681c59b4c1f25dc343a025d91cc4827.zip |
x86/mm: Avoid incomplete Global INVLPG flushes
commit ce0b15d11ad837fbacc5356941712218e38a0a83 upstream.
The INVLPG instruction is used to invalidate TLB entries for a
specified virtual address. When PCIDs are enabled, INVLPG is supposed
to invalidate TLB entries for the specified address for both the
current PCID *and* Global entries. (Note: Only kernel mappings set
Global=1.)
Unfortunately, some INVLPG implementations can leave Global
translations unflushed when PCIDs are enabled.
As a workaround, never enable PCIDs on affected processors.
I expect there to eventually be microcode mitigations to replace this
software workaround. However, the exact version numbers where that
will happen are not known today. Once the version numbers are set in
stone, the processor list can be tweaked to only disable PCIDs on
affected processors with affected microcode.
Note: if anyone wants a quick fix that doesn't require patching, just
stick 'nopcid' on your kernel command-line.
Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
Cc: stable@vger.kernel.org
Signed-off-by: Daniel Sneddon <daniel.sneddon@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions