From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1M75bd-0005yX-4c
	for qemu-devel@nongnu.org; Thu, 21 May 2009 06:34:33 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1M75bY-0005mE-TY
	for qemu-devel@nongnu.org; Thu, 21 May 2009 06:34:32 -0400
Received: from [199.232.76.173] (port=44623 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1M75bY-0005lr-3g
	for qemu-devel@nongnu.org; Thu, 21 May 2009 06:34:28 -0400
Received: from mx20.gnu.org ([199.232.41.8]:45211)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60) (envelope-from <paul@codesourcery.com>)
	id 1M75bX-00010I-FC
	for qemu-devel@nongnu.org; Thu, 21 May 2009 06:34:27 -0400
Received: from mail.codesourcery.com ([65.74.133.4])
	by mx20.gnu.org with esmtp (Exim 4.60)
	(envelope-from <paul@codesourcery.com>) id 1M75bW-0004bD-6k
	for qemu-devel@nongnu.org; Thu, 21 May 2009 06:34:26 -0400
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH] qemu: msi irq allocation api
Date: Thu, 21 May 2009 11:34:11 +0100
References: <20090520162130.GA22109@redhat.com>
	<200905211109.09844.paul@codesourcery.com>
	<4A152B8D.5020006@redhat.com>
In-Reply-To: <4A152B8D.5020006@redhat.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200905211134.21184.paul@codesourcery.com>
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: qemu-devel@nongnu.org
Cc: Carsten Otte <cotte@de.ibm.com>, kvm@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>, Rusty Russell <rusty@rustcorp.com.au>, virtualization@lists.linux-foundation.org, Christian Borntraeger <borntraeger@de.ibm.com>, Avi Kivity <avi@redhat.com>

> 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.

> 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?

Paul