From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:53038)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1StHnZ-0000dH-9m
	for qemu-devel@nongnu.org; Mon, 23 Jul 2012 08:31:46 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1StHnX-0004jz-CK
	for qemu-devel@nongnu.org; Mon, 23 Jul 2012 08:31:41 -0400
Received: from mx1.redhat.com ([209.132.183.28]:31120)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1StHnW-0004jZ-VK
	for qemu-devel@nongnu.org; Mon, 23 Jul 2012 08:31:39 -0400
Message-ID: <500D441F.2000103@redhat.com>
Date: Mon, 23 Jul 2012 15:31:27 +0300
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
References: <1342811652-16931-1-git-send-email-peter.maydell@linaro.org>
	<500A52BF.9080207@web.de>
	<CAFEAcA8DJ6mZCEbwJjSWEQRzQe58xnL47Vv-oXzEd6aP+NxKkw@mail.gmail.com>
	<500A730F.8040604@web.de>
	<CAFEAcA_Rmkcg78k0gQC0KmmXgFsOpvyPQ7LoBRKy2QXFrMnOYw@mail.gmail.com>
	<500A7A02.3050301@web.de>
	<CAFEAcA-U1AbfkVbJ1rOfGyk7_LMS0NXygoYwfq9FMDHb8xRhcg@mail.gmail.com>
	<500A8303.8020903@web.de>
	<CAFEAcA8fuAdBZb5YAyjFZMfvCWjVB5TP+VYACwrrEg7SGVSJ8g@mail.gmail.com>
	<500A8DAE.3040909@web.de>
	<CAFEAcA9gyqGpQBavR==CACNY52Gks0bGJ-22UvxsctF=hgeeLA@mail.gmail.com>
	<500AA21E.9050506@web.de>
	<CAFEAcA8GHrwvSXCfOz6v_fz3SMxBPE-Vm1P3d6_p46k1OcQJ=A@mail.gmail.com>
	<500AABC8.7080406@web.de> <20120723140418.76d8f874@BR9GNB5Z>
	<500D4129.8030200@redhat.com>
	<CAFEAcA97MjnY7obao7T0mV=i9LZRGuxVTPBhMFys0oxYAUYK0A@mail.gmail.com>
In-Reply-To: <CAFEAcA97MjnY7obao7T0mV=i9LZRGuxVTPBhMFys0oxYAUYK0A@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [PATCH] kvm: Move kvm_allows_irq0_override() to
	target-i386
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: kvm <kvm@vger.kernel.org>, patches@linaro.org, Marcelo Tosatti <mtosatti@redhat.com>, qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>, Jan Kiszka <jan.kiszka@web.de>, Cornelia Huck <cornelia.huck@de.ibm.com>

On 07/23/2012 03:25 PM, Peter Maydell wrote:
> On 23 July 2012 13:18, Avi Kivity <avi@redhat.com> wrote:
>>  While you don't have an irqchip, you do have asynchronous interrupt
>> injection, yes?  That's what irqchip really is all about.
> 
> This seems an odd point of view -- async interrupt injection
> doesn't have anything to do with whether we're modelling
> the irqchip in the kernel or in QEMU, I thought...

It does on x86.  The relationship between the APIC and the core is
synchronous - the APIC presents the interrupt, the core grabs is when it
is ready (interrupt flag, etc.) and signals the APIC it has done so.
The APIC then clears the interrupt from the interrupt request register
and sets it in the interrupt status register.  This sequence has to be
done while the vcpu is stopped, since we don't have access to the
interrupt flag otherwise.

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