summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorChris Lalancette <clalance@redhat.com>2010-06-21 11:29:40 -0400
committerAvi Kivity <avi@redhat.com>2010-08-01 10:47:17 +0300
commit529df65e394e30a78f2633b575fd81fa5b973e30 (patch)
tree03aeb13c1ae73a6ef20c704e1f2cdc0858eade5a /Documentation
parent979586e0b5809c46ebe5d784794a9f6d859b665e (diff)
downloadlinux-3.10-529df65e394e30a78f2633b575fd81fa5b973e30.tar.gz
linux-3.10-529df65e394e30a78f2633b575fd81fa5b973e30.tar.bz2
linux-3.10-529df65e394e30a78f2633b575fd81fa5b973e30.zip
KVM: Search the LAPIC's for one that will accept a PIC interrupt
Older versions of 32-bit linux have a "Checking 'hlt' instruction" test where they repeatedly call the 'hlt' instruction, and then expect a timer interrupt to kick the CPU out of halt. This happens before any LAPIC or IOAPIC setup happens, which means that all of the APIC's are in virtual wire mode at this point. Unfortunately, the current implementation of virtual wire mode is hardcoded to only kick the BSP, so if a crash+kexec occurs on a different vcpu, it will never get kicked. This patch makes pic_unlock() do the equivalent of kvm_irq_delivery_to_apic() for the IOAPIC code. That is, it runs through all of the vcpus looking for one that is in virtual wire mode. In the normal case where LAPICs and IOAPICs are configured, this won't be used at all. In the bootstrap phase of a modern OS, before the LAPICs and IOAPICs are configured, this will have exactly the same behavior as today; VCPU0 is always looked at first, so it will always get out of the loop after the first iteration. This will only go through the loop more than once during a kexec/kdump, in which case it will only do it a few times until the kexec'ed kernel programs the LAPIC and IOAPIC. Signed-off-by: Chris Lalancette <clalance@redhat.com> Signed-off-by: Avi Kivity <avi@redhat.com>
Diffstat (limited to 'Documentation')
0 files changed, 0 insertions, 0 deletions