From: Avi Kivity <avi@redhat.com>
To: Chris Lalancette <clalance@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] Search the LAPIC's for one that will accept a PIC interrupt.
Date: Wed, 23 Jun 2010 14:37:27 +0300 [thread overview]
Message-ID: <4C21F1F7.4020109@redhat.com> (raw)
In-Reply-To: <1277134180-9806-1-git-send-email-clalance@redhat.com>
On 06/21/2010 06:29 PM, Chris Lalancette wrote:
> 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.
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-06-23 11:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 15:29 [PATCH] Search the LAPIC's for one that will accept a PIC interrupt Chris Lalancette
2010-06-22 8:10 ` Gleb Natapov
2010-06-22 11:34 ` Avi Kivity
2010-06-22 11:49 ` Gleb Natapov
2010-06-22 11:54 ` Avi Kivity
2010-06-23 11:37 ` Avi Kivity [this message]
[not found] ` <20100623205619.GH2767@localhost.localdomain>
2010-06-24 3:43 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C21F1F7.4020109@redhat.com \
--to=avi@redhat.com \
--cc=clalance@redhat.com \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.