diff options
author | Thomas Gleixner <tglx@linutronix.de> | 2019-07-17 21:18:59 +0200 |
---|---|---|
committer | Thomas Gleixner <tglx@linutronix.de> | 2019-07-28 21:39:55 +0200 |
commit | f36cf386e3fec258a341d446915862eded3e13d8 (patch) | |
tree | 952026488243d73a5b57f389f6f093398860119d /Documentation/x86/conf.py | |
parent | 64dbc122b20f75183d8822618c24f85144a5a94d (diff) | |
download | linux-stable-f36cf386e3fec258a341d446915862eded3e13d8.tar.gz linux-stable-f36cf386e3fec258a341d446915862eded3e13d8.tar.bz2 linux-stable-f36cf386e3fec258a341d446915862eded3e13d8.zip |
x86/speculation/swapgs: Exclude ATOMs from speculation through SWAPGS
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>
Diffstat (limited to 'Documentation/x86/conf.py')
0 files changed, 0 insertions, 0 deletions