From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1M763R-0006Yr-9p
	for qemu-devel@nongnu.org; Thu, 21 May 2009 07:03:17 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1M763M-0006Xp-Gd
	for qemu-devel@nongnu.org; Thu, 21 May 2009 07:03:16 -0400
Received: from [199.232.76.173] (port=33503 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1M763M-0006Xm-Cf
	for qemu-devel@nongnu.org; Thu, 21 May 2009 07:03:12 -0400
Received: from mx2.redhat.com ([66.187.237.31]:56708)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <avi@redhat.com>) id 1M763L-0004XE-Po
	for qemu-devel@nongnu.org; Thu, 21 May 2009 07:03:12 -0400
Message-ID: <4A15346C.8090906@redhat.com>
Date: Thu, 21 May 2009 14:01:00 +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>
	<200905211109.09844.paul@codesourcery.com>
	<4A152B8D.5020006@redhat.com>
	<200905211134.21184.paul@codesourcery.com>
In-Reply-To: <200905211134.21184.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 PCI bus doesn't need any special support (I think) but something on
>> the other end needs to interpret those writes.
>>     
>
> Sure. But there's definitely nothing PCI specific about it. I assumed this 
> would all be contained within the APIC.
>   

MSIs are defined by PCI and their configuration is done using the PCI 
configuration space.

>> In any case we need some internal API for this, and qemu_irq looks like
>> a good choice.
>>     
>
> What do you expect to be using this API?
>   

virtio, emulated devices capable of supporting MSI (e1000?), device 
assignment (not yet in qemu.git).

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