From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH] Search the LAPIC's for one that will accept a PIC interrupt. Date: Tue, 22 Jun 2010 14:54:03 +0300 Message-ID: <4C20A45B.1010307@redhat.com> References: <1277134180-9806-1-git-send-email-clalance@redhat.com> <20100622081021.GV4689@redhat.com> <4C209FC5.40201@redhat.com> <20100622114903.GW4689@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Chris Lalancette , kvm@vger.kernel.org To: Gleb Natapov Return-path: Received: from mx1.redhat.com ([209.132.183.28]:43664 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754831Ab0FVLyE (ORCPT ); Tue, 22 Jun 2010 07:54:04 -0400 Received: from int-mx08.intmail.prod.int.phx2.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.21]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id o5MBs4IJ027013 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 22 Jun 2010 07:54:04 -0400 Received: from cleopatra.tlv.redhat.com (cleopatra.tlv.redhat.com [10.35.255.11]) by int-mx08.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id o5MBs3C3018023 for ; Tue, 22 Jun 2010 07:54:04 -0400 In-Reply-To: <20100622114903.GW4689@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: 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