Avi Kivity 46a929bc15 KVM: avoid taking ioapic mutex for non-ioapic EOIs ... When the guest acknowledges an interrupt, it sends an EOI message to the local apic, which broadcasts it to the ioapic. To handle the EOI, we need to take the ioapic mutex. On large guests, this causes a lot of contention on this mutex. Since large guests usually don't route interrupts via the ioapic (they use msi instead), this is completely unnecessary. Avoid taking the mutex by introducing a handled_vectors bitmap. Before taking the mutex, check if the ioapic was actually responsible for the acked vector. If not, we can return early. Signed-off-by: Avi Kivity <avi@redhat.com> Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>		2010-03-01 12:35:46 -03:00
..
kvm	KVM: avoid taking ioapic mutex for non-ioapic EOIs	2010-03-01 12:35:46 -03:00