diff options
| author | Alex Williamson | 2011-07-14 21:27:03 +0200 |
|---|---|---|
| committer | Avi Kivity | 2011-07-24 10:50:42 +0200 |
| commit | 3f68b0318bbbd61bf08478ab99a149f0d9e5156e (patch) | |
| tree | 5caa009c012cee6b61de36f1aa643c9443684423 /kernel | |
| parent | KVM: MMU: trace mmio page fault (diff) | |
| download | kernel-qcow2-linux-3f68b0318bbbd61bf08478ab99a149f0d9e5156e.tar.gz kernel-qcow2-linux-3f68b0318bbbd61bf08478ab99a149f0d9e5156e.tar.xz kernel-qcow2-linux-3f68b0318bbbd61bf08478ab99a149f0d9e5156e.zip | |
KVM: IOMMU: Disable device assignment without interrupt remapping
IOMMU interrupt remapping support provides a further layer of
isolation for device assignment by preventing arbitrary interrupt
block DMA writes by a malicious guest from reaching the host. By
default, we should require that the platform provides interrupt
remapping support, with an opt-in mechanism for existing behavior.
Both AMD IOMMU and Intel VT-d2 hardware support interrupt
remapping, however we currently only have software support on
the Intel side. Users wishing to re-enable device assignment
when interrupt remapping is not supported on the platform can
use the "allow_unsafe_assigned_interrupts=1" module option.
[avi: break long lines]
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
Signed-off-by: Avi Kivity <avi@redhat.com>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions