aboutsummaryrefslogtreecommitdiff
path: root/hw/vfio
diff options
context:
space:
mode:
authorAlexey Kardashevskiy <aik@ozlabs.ru>2016-07-04 13:33:03 +1000
committerDavid Gibson <david@gibson.dropbear.id.au>2016-07-05 10:43:02 +1000
commit606b54986df4e3964eee2d74460bd06ed2f384e5 (patch)
tree28cb52bf019affa317ac58645997c9f398409c47 /hw/vfio
parentc4e6c42353fe735add45b790f8d3a323590f7cab (diff)
downloadqemu-606b54986df4e3964eee2d74460bd06ed2f384e5.zip
qemu-606b54986df4e3964eee2d74460bd06ed2f384e5.tar.gz
qemu-606b54986df4e3964eee2d74460bd06ed2f384e5.tar.bz2
spapr_iommu: Realloc guest visible TCE table when starting/stopping listening
The sPAPR TCE tables manage 2 copies when VFIO is using an IOMMU - a guest view of the table and a hardware TCE table. If there is no VFIO presense in the address space, then just the guest view is used, if this is the case, it is allocated in the KVM. However since there is no support yet for VFIO in KVM TCE hypercalls, when we start using VFIO, we need to move the guest view from KVM to the userspace; and we need to do this for every IOMMU on a bus with VFIO devices. This implements the callbacks for the sPAPR IOMMU - notify_started() reallocated the guest view to the user space, notify_stopped() does the opposite. This removes explicit spapr_tce_set_need_vfio() call from PCI hotplug path as the new callbacks do this better - they notify IOMMU at the exact moment when the configuration is changed, and this also includes the case of PCI hot unplug. Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru> Reviewed-by: David Gibson <david@gibson.dropbear.id.au> Acked-by: Alex Williamson <alex.williamson@redhat.com> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Diffstat (limited to 'hw/vfio')
0 files changed, 0 insertions, 0 deletions