All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Chris Lalancette <clalance@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH] Search the LAPIC's for one that will accept a PIC interrupt.
Date: Tue, 22 Jun 2010 14:54:03 +0300	[thread overview]
Message-ID: <4C20A45B.1010307@redhat.com> (raw)
In-Reply-To: <20100622114903.GW4689@redhat.com>

On 06/22/2010 02:49 PM, Gleb Natapov wrote:
>
>
>> There's a slight issue in that if an interrupt happens while a vcpu
>> is turning off LVT0.ExtInt, the interrupt gets lost.  But this is
>> better than what we have now.
>>
>>      
> We can check pic output after LVT0.ExtInt is configured.
>
>    

Right.

>> btw, I think virtual wire refers to:
>>
>>    pic ->  ioapic(ExtInt) ->  (apic bus) ->  lapic
>>
>> (virtual wire since the interrupt is passed over the apic bus, not a
>> real wire)
>>
>> while our configuration is
>>
>>    pic ->  lint0 ->  lapic lvt0 (ExtInt)
>>
>>      
> I saw both referred as virtual wire, may be erroneous.
>
> How is the mode where lapic is disabled and pic interrupts are delivered
> directly to cpu is called?
>    

I'm just guessing based on the name, no idea really.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2010-06-22 11:54 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 [this message]
2010-06-23 11:37 ` Avi Kivity
     [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=4C20A45B.1010307@redhat.com \
    --to=avi@redhat.com \
    --cc=clalance@redhat.com \
    --cc=gleb@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.