summaryrefslogtreecommitdiff
path: root/fs/gfs2/main.c
diff options
context:
space:
mode:
authorPaolo Bonzini <pbonzini@redhat.com>2024-09-15 09:49:33 +0300
committerPaolo Bonzini <pbonzini@redhat.com>2024-09-15 09:49:33 +0300
commit9d70f3fec14421e793ffbc0ec2f739b24e534900 (patch)
tree1aa0c53f2bef7fa4f49304b064d4db6a538e97f6 /fs/gfs2/main.c
parent59cbd4eea48fdbc68fc17a29ad71188fea74b28b (diff)
downloadlinux-9d70f3fec14421e793ffbc0ec2f739b24e534900.tar.xz
Revert "KVM: VMX: Always honor guest PAT on CPUs that support self-snoop"
This reverts commit 377b2f359d1f71c75f8cc352b5c81f2210312d83. This caused a regression with the bochsdrm driver, which used ioremap() instead of ioremap_wc() to map the video RAM. After the commit, the WB memory type is used without the IGNORE_PAT, resulting in the slower UC memory type. In fact, UC is slow enough to basically cause guests to not boot... but only on new processors such as Sapphire Rapids and Cascade Lake. Coffee Lake for example works properly, though that might also be an effect of being on a larger, more NUMA system. The driver has been fixed but that does not help older guests. Until we figure out whether Cascade Lake and newer processors are working as intended, revert the commit. Long term we might add a quirk, but the details depend on whether the processors are working as intended: for example if they are, the quirk might reference bochs-compatible devices, e.g. in the name and documentation, so that userspace can disable the quirk by default and only leave it enabled if such a device is being exposed to the guest. If instead this is actually a bug in CLX+, then the actions we need to take are different and depend on the actual cause of the bug. Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'fs/gfs2/main.c')
0 files changed, 0 insertions, 0 deletions