From: "Michael S. Tsirkin" <mst@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Carsten Otte <cotte@de.ibm.com>,
kvm@vger.kernel.org, qemu-devel@nongnu.org,
virtualization@lists.linux-foundation.org,
Christian Borntraeger <borntraeger@de.ibm.com>,
avi@redhat.com, Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] [PATCH] qemu: msi irq allocation api
Date: Wed, 20 May 2009 21:28:18 +0300 [thread overview]
Message-ID: <20090520182818.GC22935@redhat.com> (raw)
In-Reply-To: <f43fc5580905201044u48a12c13pa8961b7663d1a7bf@mail.gmail.com>
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?
--
MST
next prev parent reply other threads:[~2009-05-20 18:28 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090520162130.GA22109@redhat.com>
2009-05-20 17:21 ` [Qemu-devel] [PATCH] qemu: msi irq allocation api Blue Swirl
[not found] ` <f43fc5580905201021x265ffb8ax36b04a740c9fe92@mail.gmail.com>
2009-05-20 17:32 ` Avi Kivity
2009-05-20 17:35 ` Michael S. Tsirkin
[not found] ` <4A143EB9.6080202@redhat.com>
2009-05-20 17:40 ` Blue Swirl
[not found] ` <20090520173536.GA22935@redhat.com>
2009-05-20 17:44 ` Blue Swirl
[not found] ` <f43fc5580905201044u48a12c13pa8961b7663d1a7bf@mail.gmail.com>
2009-05-20 18:24 ` Michael S. Tsirkin
2009-05-20 18:28 ` Michael S. Tsirkin [this message]
2009-05-20 18:38 ` Blue Swirl
[not found] ` <f43fc5580905201138g52df3570r29242cc50cbbe83a@mail.gmail.com>
2009-05-20 20:02 ` Michael S. Tsirkin
[not found] ` <20090520200224.GA23500@redhat.com>
2009-05-20 20:17 ` Michael S. Tsirkin
2009-05-20 20:18 ` Blue Swirl
[not found] ` <20090520201733.GA23518@redhat.com>
2009-05-20 20:26 ` Blue Swirl
[not found] ` <f43fc5580905201326p2472ef1dyf9269c5c21b527ef@mail.gmail.com>
2009-05-20 20:33 ` Michael S. Tsirkin
[not found] ` <20090520203335.GC23518@redhat.com>
2009-05-20 20:44 ` Blue Swirl
[not found] ` <f43fc5580905201344v23e15851u4a7517b9da879604@mail.gmail.com>
2009-05-21 9:24 ` Michael S. Tsirkin
[not found] ` <f43fc5580905201318l7d9d2d5ah8fc0745950c52167@mail.gmail.com>
2009-05-20 20:29 ` Michael S. Tsirkin
2009-05-21 10:09 ` Paul Brook
[not found] ` <200905211109.09844.paul@codesourcery.com>
2009-05-21 10:23 ` Avi Kivity
[not found] ` <4A152B8D.5020006@redhat.com>
2009-05-21 10:34 ` Paul Brook
[not found] ` <200905211134.21184.paul@codesourcery.com>
2009-05-21 10:50 ` Michael S. Tsirkin
2009-05-21 11:01 ` Avi Kivity
[not found] ` <4A15346C.8090906@redhat.com>
2009-05-21 12:01 ` Paul Brook
[not found] ` <200905211301.52089.paul@codesourcery.com>
2009-05-21 12:08 ` Avi Kivity
[not found] ` <4A154432.1060808@redhat.com>
2009-05-21 12:14 ` Michael S. Tsirkin
2009-05-21 12:29 ` Paul Brook
[not found] ` <200905211329.41578.paul@codesourcery.com>
2009-05-21 12:38 ` Avi Kivity
2009-05-21 13:06 ` Michael S. Tsirkin
[not found] ` <4A154B60.4080701@redhat.com>
2009-05-21 13:08 ` Michael S. Tsirkin
2009-05-21 13:09 ` Paul Brook
2009-05-21 13:11 ` Michael S. Tsirkin
[not found] ` <200905211409.33325.paul@codesourcery.com>
2009-05-21 13:12 ` Michael S. Tsirkin
[not found] ` <20090521131231.GH25309@redhat.com>
2009-05-21 13:23 ` Paul Brook
[not found] ` <200905211423.20843.paul@codesourcery.com>
2009-05-21 13:31 ` Paul Brook
2009-05-21 13:46 ` Michael S. Tsirkin
[not found] ` <20090521134650.GI25309@redhat.com>
2009-05-21 13:53 ` Paul Brook
[not found] ` <200905211453.14691.paul@codesourcery.com>
2009-05-21 14:01 ` Avi Kivity
2009-05-21 14:07 ` Michael S. Tsirkin
[not found] ` <4A155EC6.6070501@redhat.com>
2009-05-21 14:14 ` Paul Brook
[not found] ` <200905211514.31059.paul@codesourcery.com>
2009-05-21 14:37 ` Avi Kivity
[not found] ` <4A156739.6060207@redhat.com>
2009-05-21 14:50 ` Paul Brook
[not found] ` <200905211550.21217.paul@codesourcery.com>
2009-05-21 14:54 ` Avi Kivity
[not found] ` <4A156B41.4090608@redhat.com>
2009-05-21 15:01 ` Paul Brook
[not found] ` <200905211601.33164.paul@codesourcery.com>
2009-05-21 15:11 ` Avi Kivity
2009-05-21 16:49 ` Michael S. Tsirkin
[not found] ` <20090521140711.GJ25309@redhat.com>
2009-05-24 11:14 ` Avi Kivity
2009-05-21 14:46 ` Michael S. Tsirkin
[not found] ` <200905211431.27287.paul@codesourcery.com>
2009-05-21 16:45 ` Michael S. Tsirkin
[not found] ` <20090521164520.GA6474@redhat.com>
2009-05-21 17:33 ` Michael S. Tsirkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090520182818.GC22935@redhat.com \
--to=mst@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=borntraeger@de.ibm.com \
--cc=cotte@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).