Jan Kiszka 07975ad3b3 KVM: Introduce direct MSI message injection for in-kernel irqchips ... Currently, MSI messages can only be injected to in-kernel irqchips by defining a corresponding IRQ route for each message. This is not only unhandy if the MSI messages are generated "on the fly" by user space, IRQ routes are a limited resource that user space has to manage carefully. By providing a direct injection path, we can both avoid using up limited resources and simplify the necessary steps for user land. Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com> Signed-off-by: Avi Kivity <avi@redhat.com>		2012-04-24 15:59:47 +03:00
..
assigned-dev.c	KVM: Convert intx_mask_lock to spin lock	2012-03-20 12:41:24 +02:00
async_pf.c	KVM: fix the race while wakeup all pv guest	2011-01-12 11:29:03 +02:00
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: dont clear TMR on EOI	2012-04-16 20:36:38 -03:00
ioapic.h	KVM: dont clear TMR on EOI	2012-04-16 20:36:38 -03:00
iodev.h
iommu.c	KVM: lock slots_lock around device assignment	2012-04-19 00:04:18 -03:00
irq_comm.c	KVM: Introduce direct MSI message injection for in-kernel irqchips	2012-04-24 15:59:47 +03:00
Kconfig	KVM: Introduce direct MSI message injection for in-kernel irqchips	2012-04-24 15:59:47 +03:00
kvm_main.c	KVM: Introduce direct MSI message injection for in-kernel irqchips	2012-04-24 15:59:47 +03:00