diff options
author | Ankit Agrawal <[email protected]> | 2024-02-24 20:35:46 +0530 |
---|---|---|
committer | Oliver Upton <[email protected]> | 2024-02-24 17:57:39 +0000 |
commit | a39d3a966a090989b89c0287a67cd98c85ae2f52 (patch) | |
tree | e2c35f635f3b45e03a29ce6e86c0f0f73b845a46 /scripts/gdb/linux/pgtable.py | |
parent | 8c47ce3e1d2c285349edf426b98e8460ce3e2f33 (diff) |
vfio: Convey kvm that the vfio-pci device is wc safe
The VM_ALLOW_ANY_UNCACHED flag is implemented for ARM64,
allowing KVM stage 2 device mapping attributes to use Normal-NC
rather than DEVICE_nGnRE, which allows guest mappings supporting
write-combining attributes (WC). ARM does not architecturally
guarantee this is safe, and indeed some MMIO regions like the GICv2
VCPU interface can trigger uncontained faults if Normal-NC is used.
To safely use VFIO in KVM the platform must guarantee full safety
in the guest where no action taken against a MMIO mapping can
trigger an uncontained failure. The expectation is that most VFIO PCI
platforms support this for both mapping types, at least in common
flows, based on some expectations of how PCI IP is integrated. So
make vfio-pci set the VM_ALLOW_ANY_UNCACHED flag.
Suggested-by: Catalin Marinas <[email protected]>
Acked-by: Jason Gunthorpe <[email protected]>
Acked-by: Catalin Marinas <[email protected]>
Acked-by: Alex Williamson <[email protected]>
Reviewed-by: David Hildenbrand <[email protected]>
Reviewed-by: Marc Zyngier <[email protected]>
Signed-off-by: Ankit Agrawal <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Oliver Upton <[email protected]>
Diffstat (limited to 'scripts/gdb/linux/pgtable.py')
0 files changed, 0 insertions, 0 deletions