diff options
author | Sean Christopherson <seanjc@google.com> | 2024-03-09 04:09:29 +0300 |
---|---|---|
committer | Sean Christopherson <seanjc@google.com> | 2024-06-07 17:18:03 +0300 |
commit | 377b2f359d1f71c75f8cc352b5c81f2210312d83 (patch) | |
tree | e552a7308bad09bcf189b0e81983b02ce8a87e94 /scripts/generate_rust_analyzer.py | |
parent | 65a4de0ffd975af7e2ffc9acb875b6a8ae7ee1aa (diff) | |
download | linux-377b2f359d1f71c75f8cc352b5c81f2210312d83.tar.xz |
KVM: VMX: Always honor guest PAT on CPUs that support self-snoop
Unconditionally honor guest PAT on CPUs that support self-snoop, as
Intel has confirmed that CPUs that support self-snoop always snoop caches
and store buffers. I.e. CPUs with self-snoop maintain cache coherency
even in the presence of aliased memtypes, thus there is no need to trust
the guest behaves and only honor PAT as a last resort, as KVM does today.
Honoring guest PAT is desirable for use cases where the guest has access
to non-coherent DMA _without_ bouncing through VFIO, e.g. when a virtual
(mediated, for all intents and purposes) GPU is exposed to the guest, along
with buffers that are consumed directly by the physical GPU, i.e. which
can't be proxied by the host to ensure writes from the guest are performed
with the correct memory type for the GPU.
Cc: Yiwei Zhang <zzyiwei@google.com>
Suggested-by: Yan Zhao <yan.y.zhao@intel.com>
Suggested-by: Kevin Tian <kevin.tian@intel.com>
Tested-by: Xiangfei Ma <xiangfeix.ma@intel.com>
Tested-by: Yongwei Ma <yongwei.ma@intel.com>
Link: https://lore.kernel.org/r/20240309010929.1403984-6-seanjc@google.com
Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions