Alex Williamson 21a1416a1c KVM: lock slots_lock around device assignment ... As pointed out by Jason Baron, when assigning a device to a guest we first set the iommu domain pointer, which enables mapping and unmapping of memory slots to the iommu. This leaves a window where this path is enabled, but we haven't synchronized the iommu mappings to the existing memory slots. Thus a slot being removed at that point could send us down unexpected code paths removing non-existent pinnings and iommu mappings. Take the slots_lock around creating the iommu domain and initial mappings as well as around iommu teardown to avoid this race. Signed-off-by: Alex Williamson <alex.williamson@redhat.com> Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>		2012-04-19 00:04:18 -03:00
..
assigned-dev.c	KVM: Convert intx_mask_lock to spin lock	2012-03-20 12:41:24 +02:00
async_pf.c
async_pf.h
coalesced_mmio.c	KVM: make checks stricter in coalesced_mmio_in_range()	2011-12-27 11:17:07 +02:00
coalesced_mmio.h	KVM: Make coalesced mmio use a device per zone	2011-09-25 19:17:57 +03:00
eventfd.c	KVM: Intelligent device lookup on I/O bus	2011-09-25 19:17:59 +03:00
ioapic.c	KVM: drop bsp_vcpu pointer from kvm struct	2011-12-27 11:22:32 +02:00
ioapic.h
iodev.h
iommu.c	KVM: lock slots_lock around device assignment	2012-04-19 00:04:18 -03:00
irq_comm.c
Kconfig
kvm_main.c	KVM: unmap pages from the iommu when slots are removed	2012-04-11 22:55:25 -03:00