aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
diff options
context:
space:
mode:
authorPaolo Bonzini <[email protected]>2025-07-28 15:04:27 +0000
committerPaolo Bonzini <[email protected]>2025-07-29 12:36:28 +0000
commitf05efcfe07d8af26703b75cb91c8f58924661275 (patch)
tree2df151290f60c6d4aaf10fde7bfeb10828d107fd /drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
parentMerge tag 'kvm-x86-irqs-6.17' of https://github.com/kvm-x86/linux into HEAD (diff)
parentKVM: VMX: Apply MMIO Stale Data mitigation if KVM maps MMIO into the guest (diff)
downloadkernel-f05efcfe07d8af26703b75cb91c8f58924661275.tar.gz
kernel-f05efcfe07d8af26703b75cb91c8f58924661275.zip
Merge tag 'kvm-x86-mmio-6.17' of https://github.com/kvm-x86/linux into HEAD
KVM MMIO Stale Data mitigation cleanup for 6.17 Rework KVM's mitigation for the MMIO State Data vulnerability to track whether or not a vCPU has access to (host) MMIO based on the MMU that will be used when running in the guest. The current approach doesn't actually detect whether or not a guest has access to MMIO, and is prone to false negatives (and to a lesser extent, false positives), as KVM_DEV_VFIO_FILE_ADD is optional, and obviously only covers VFIO devices.
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_device.c')
0 files changed, 0 insertions, 0 deletions