You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

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>		13 years ago
..
Kconfig	…
assigned-dev.c	…
async_pf.c	…
async_pf.h	…
coalesced_mmio.c	…
coalesced_mmio.h	…
eventfd.c	…
ioapic.c	…
ioapic.h	…
iodev.h	…
iommu.c	KVM: lock slots_lock around device assignment	13 years ago
irq_comm.c	…
kvm_main.c	…