diff options
author | 2020-08-23 11:21:16 -0700 | |
---|---|---|
committer | 2020-08-23 11:21:16 -0700 | |
commit | 550c2129d93d5eb198835ac83c05ef672e8c491c (patch) | |
tree | 922fe5453bb6d9c4e0c8091d2d3149089706f93d /drivers/gpu/drm/amd/display/dc/core/dc_link_dp.c | |
parent | Merge tag 'perf-urgent-2020-08-23' of git://git.kernel.org/pub/scm/linux/kern... (diff) | |
parent | x86/entry/64: Do not use RDPID in paranoid entry to accomodate KVM (diff) | |
download | linux-550c2129d93d5eb198835ac83c05ef672e8c491c.tar.gz linux-550c2129d93d5eb198835ac83c05ef672e8c491c.tar.bz2 linux-550c2129d93d5eb198835ac83c05ef672e8c491c.zip |
Merge tag 'x86-urgent-2020-08-23' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Pull x86 fix from Thomas Gleixner:
"A single fix for x86 which removes the RDPID usage from the paranoid
entry path and unconditionally uses LSL to retrieve the CPU number.
RDPID depends on MSR_TSX_AUX. KVM has an optmization to avoid
expensive MRS read/writes on VMENTER/EXIT. It caches the MSR values
and restores them either when leaving the run loop, on preemption or
when going out to user space. MSR_TSX_AUX is part of that lazy MSR
set, so after writing the guest value and before the lazy restore any
exception using the paranoid entry will read the guest value and use
it as CPU number to retrieve the GSBASE value for the current CPU when
FSGSBASE is enabled. As RDPID is only used in that particular entry
path, there is no reason to burden VMENTER/EXIT with two extra MSR
writes. Remove the RDPID optimization, which is not even backed by
numbers from the paranoid entry path instead"
* tag 'x86-urgent-2020-08-23' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
x86/entry/64: Do not use RDPID in paranoid entry to accomodate KVM
Diffstat (limited to 'drivers/gpu/drm/amd/display/dc/core/dc_link_dp.c')
0 files changed, 0 insertions, 0 deletions