summaryrefslogtreecommitdiffstats
path: root/Documentation
diff options
context:
space:
mode:
authorThomas Gleixner <tglx@linutronix.de>2019-07-17 21:18:59 +0200
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2019-08-06 19:06:58 +0200
commitb88241aef6f1654417bb281546da316ffab57807 (patch)
tree9ecf6bac8bebfe7d0ca2d1361017679dc178f7de /Documentation
parent931b6bfe8af1069fd1a494ef6ab14509ffeacdc3 (diff)
downloadlinux-stable-b88241aef6f1654417bb281546da316ffab57807.tar.gz
linux-stable-b88241aef6f1654417bb281546da316ffab57807.tar.bz2
linux-stable-b88241aef6f1654417bb281546da316ffab57807.zip
x86/speculation/swapgs: Exclude ATOMs from speculation through SWAPGS
commit f36cf386e3fec258a341d446915862eded3e13d8 upstream Intel provided the following information: On all current Atom processors, instructions that use a segment register value (e.g. a load or store) will not speculatively execute before the last writer of that segment retires. Thus they will not use a speculatively written segment value. That means on ATOMs there is no speculation through SWAPGS, so the SWAPGS entry paths can be excluded from the extra LFENCE if PTI is disabled. Create a separate bug flag for the through SWAPGS speculation and mark all out-of-order ATOMs and AMD/HYGON CPUs as not affected. The in-order ATOMs are excluded from the whole mitigation mess anyway. Reported-by: Andrew Cooper <andrew.cooper3@citrix.com> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Reviewed-by: Tyler Hicks <tyhicks@canonical.com> Reviewed-by: Josh Poimboeuf <jpoimboe@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'Documentation')
0 files changed, 0 insertions, 0 deletions