From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1M6qgy-0004Yi-3Z
	for qemu-devel@nongnu.org; Wed, 20 May 2009 14:39:04 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1M6qgt-0004Vs-Ty
	for qemu-devel@nongnu.org; Wed, 20 May 2009 14:39:03 -0400
Received: from [199.232.76.173] (port=40910 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1M6qgt-0004Vh-Kr
	for qemu-devel@nongnu.org; Wed, 20 May 2009 14:38:59 -0400
Received: from mail-bw0-f175.google.com ([209.85.218.175]:54316)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <blauwirbel@gmail.com>) id 1M6qgt-0006rr-6u
	for qemu-devel@nongnu.org; Wed, 20 May 2009 14:38:59 -0400
Received: by bwz23 with SMTP id 23so548240bwz.34
	for <qemu-devel@nongnu.org>; Wed, 20 May 2009 11:38:58 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <20090520182818.GC22935@redhat.com>
References: <20090520162130.GA22109@redhat.com>
	<f43fc5580905201021x265ffb8ax36b04a740c9fe92@mail.gmail.com>
	<20090520173536.GA22935@redhat.com>
	<f43fc5580905201044u48a12c13pa8961b7663d1a7bf@mail.gmail.com>
	<20090520182818.GC22935@redhat.com>
Date: Wed, 20 May 2009 21:38:58 +0300
Message-ID: <f43fc5580905201138g52df3570r29242cc50cbbe83a@mail.gmail.com>
Subject: Re: [Qemu-devel] [PATCH] qemu: msi irq allocation api
From: Blue Swirl <blauwirbel@gmail.com>
Content-Type: text/plain; charset=UTF-8
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: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Carsten Otte <cotte@de.ibm.com>, kvm@vger.kernel.org, Rusty Russell <rusty@rustcorp.com.au>, qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org, Christian Borntraeger <borntraeger@de.ibm.com>, avi@redhat.com

On 5/20/09, Michael S. Tsirkin <mst@redhat.com> wrote:
> On Wed, May 20, 2009 at 08:44:31PM +0300, Blue Swirl wrote:
>  > On 5/20/09, Michael S. Tsirkin <mst@redhat.com> wrote:
>  > > On Wed, May 20, 2009 at 08:21:01PM +0300, Blue Swirl wrote:
>  > >  > On 5/20/09, Michael S. Tsirkin <mst@redhat.com> wrote:
>  > >  > > define api for allocating/setting up msi-x irqs, and for updating them
>  > >  > >  with msi-x vector information, supply implementation in ioapic. Please
>  > >  > >  comment on this API: I intend to port my msi-x patch to work on top of
>  > >  > >  it.
>  > >  > >
>  > >  > >  Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
>  > >  >
>  > >  > Sparc64 also uses packets ("mondos", not implemented yet) for
>  > >  > interrupt vector data, there the packet size is 8 * 64 bits.
>  > >  > I think we should aim for a more generic API that covers this case also.
>  > >
>  > >
>  > > Are you sure this is a good idea? MSI is tied to PCI, and PCI only has
>  > >  MSI, not "mondos". What code would benefit from this abstraction?
>  >
>  > Sparc64 emulation, of course. I think also the API would be neater.
>
>
> Since "mondos" are not interrupts, why use irqs for them?

I just said above that they are used for interrupt vector data. What
makes you think they are not interrupts?