diff options
author | Juergen Gross <jgross@suse.com> | 2022-11-02 10:47:10 +0300 |
---|---|---|
committer | Borislav Petkov <bp@suse.de> | 2022-11-10 15:12:45 +0300 |
commit | adfe7512e1d0b2e83215b0ec56337d2df9f1032d (patch) | |
tree | 1b7098e1bc66f88da331abff517161e9b5788d16 /include/linux/cpuhotplug.h | |
parent | 0b9a6a8bedbfb38e7c6be4d119a267e6277307cc (diff) | |
download | linux-adfe7512e1d0b2e83215b0ec56337d2df9f1032d.tar.xz |
x86: Decouple PAT and MTRR handling
Today, PAT is usable only with MTRR being active, with some nasty tweaks
to make PAT usable when running as a Xen PV guest which doesn't support
MTRR.
The reason for this coupling is that both PAT MSR changes and MTRR
changes require a similar sequence and so full PAT support was added
using the already available MTRR handling.
Xen PV PAT handling can work without MTRR, as it just needs to consume
the PAT MSR setting done by the hypervisor without the ability and need
to change it. This in turn has resulted in a convoluted initialization
sequence and wrong decisions regarding cache mode availability due to
misguiding PAT availability flags.
Fix all of that by allowing to use PAT without MTRR and by reworking
the current PAT initialization sequence to match better with the newly
introduced generic cache initialization.
This removes the need of the recently added pat_force_disabled flag, so
remove the remnants of the patch adding it.
Signed-off-by: Juergen Gross <jgross@suse.com>
Signed-off-by: Borislav Petkov <bp@suse.de>
Link: https://lore.kernel.org/r/20221102074713.21493-14-jgross@suse.com
Signed-off-by: Borislav Petkov <bp@suse.de>
Diffstat (limited to 'include/linux/cpuhotplug.h')
0 files changed, 0 insertions, 0 deletions