| commit | c3388c9bd8d4f4fd841b521feed20993185d9be4 | |
| author | Jan Kiszka <jan.kiszka@siemens.com> | |
| Mon, 6 Feb 2012 11:20:53 +0000 (6 12:20 +0100) | ||
| committer | Marcelo Tosatti <mtosatti@redhat.com> | |
| Wed, 8 Feb 2012 17:48:02 +0000 (8 15:48 -0200) | ||
| tree | 6c30538a467df245d4e2f6467691509758d8cd37 | treesnapshot (tar.gz zip) |
| parent | a6b402c989cc83e38bdbccf570296eb8d64fe5af | commitdiff |
qemu-kvm: Fix GSI handling with in-kernel irqchip
Interrupt routing with in-kernel irqchip was always a mess. Now this
increased after latest upstream merge: we started to call ioapic_set_irq
also for kernel-handled interrupts.
Reduce this mess again by using the upstream kvm_piix3_gsi_handler. It
is aware of the PIIX3-specific routing in KVM mode and won't call into
the user space APIC model (as we do not raise IRQs >= ISA_NUM_IRQS with
the PIIX3).
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
Interrupt routing with in-kernel irqchip was always a mess. Now this
increased after latest upstream merge: we started to call ioapic_set_irq
also for kernel-handled interrupts.
Reduce this mess again by using the upstream kvm_piix3_gsi_handler. It
is aware of the PIIX3-specific routing in KVM mode and won't call into
the user space APIC model (as we do not raise IRQs >= ISA_NUM_IRQS with
the PIIX3).
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
| hw/pc_piix.c | diffblobblamehistory |