From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1M79yl-0005lK-AO
	for qemu-devel@nongnu.org; Thu, 21 May 2009 11:14:43 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1M79yf-0005ch-B0
	for qemu-devel@nongnu.org; Thu, 21 May 2009 11:14:42 -0400
Received: from [199.232.76.173] (port=44309 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1M79yf-0005cU-6P
	for qemu-devel@nongnu.org; Thu, 21 May 2009 11:14:37 -0400
Received: from mx2.redhat.com ([66.187.237.31]:36512)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <avi@redhat.com>) id 1M79yX-0003es-Kq
	for qemu-devel@nongnu.org; Thu, 21 May 2009 11:14:30 -0400
Message-ID: <4A156F2E.4050802@redhat.com>
Date: Thu, 21 May 2009 18:11:42 +0300
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH] qemu: msi irq allocation api
References: <20090520162130.GA22109@redhat.com>
	<200905211550.21217.paul@codesourcery.com>
	<4A156B41.4090608@redhat.com>
	<200905211601.33164.paul@codesourcery.com>
In-Reply-To: <200905211601.33164.paul@codesourcery.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Paul Brook <paul@codesourcery.com>
Cc: Carsten Otte <cotte@de.ibm.com>, kvm@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>, Rusty Russell <rusty@rustcorp.com.au>, qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org, Christian Borntraeger <borntraeger@de.ibm.com>

Paul Brook wrote:
>> The fast path is an eventfd so that we don't have to teach all the
>> clients about the details of MSI.  Userspace programs the MSI details
>> into kvm and hands the client an eventfd.  All the client has to do is
>> bang on the eventfd for the interrupt to be queued.  The eventfd
>> provides event coalescing and is equally useful from the kernel and
>> userspace, and can be used with targets other than kvm.
>>     
>
> So presumably if a device triggers an APIC interrupt using a write that isn't 
> one of the currently configured PCI devices, it all explodes horribly?
>   

I don't follow.  Can you elaborate on your scenario?

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