Gleb Natapov 4925663a07 KVM: Report IRQ injection status to userspace. ...

IRQ injection status is either -1 (if there was no CPU found
that should except the interrupt because IRQ was masked or
ioapic was misconfigured or ...) or >= 0 in that case the
number indicates to how many CPUs interrupt was injected.
If the value is 0 it means that the interrupt was coalesced
and probably should be reinjected.

Signed-off-by: Gleb Natapov <gleb@redhat.com>
Signed-off-by: Avi Kivity <avi@redhat.com>

2009-03-24 11:03:11 +02:00

..

coalesced_mmio.c

KVM: Add coalesced MMIO support (common part)

2008-07-20 12:42:31 +03:00

coalesced_mmio.h

KVM: Add coalesced MMIO support (common part)

2008-07-20 12:42:31 +03:00

ioapic.c

KVM: Report IRQ injection status to userspace.

2009-03-24 11:03:11 +02:00

ioapic.h

KVM: Report IRQ injection status to userspace.

2009-03-24 11:03:11 +02:00

iodev.h

KVM: kvm_io_device: extend in_range() to manage len and write attribute

2008-07-20 12:42:30 +03:00

iommu.c

KVM: Fix assigned devices circular locking dependency

2009-02-15 02:47:39 +02:00

irq_comm.c

KVM: Report IRQ injection status to userspace.

2009-03-24 11:03:11 +02:00

kvm_main.c

KVM: MMU: handle compound pages in kvm_is_mmio_pfn

2009-03-24 11:03:09 +02:00

kvm_trace.c

KVM: Prevent trace call into unloaded module text

2008-12-31 16:55:04 +02:00