From: "Michael S. Tsirkin" <mst@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 2/2] virtio: enable msi-x for console+balloon
Date: Mon, 7 Dec 2009 16:43:14 +0200 [thread overview]
Message-ID: <20091207144314.GA5734@redhat.com> (raw)
In-Reply-To: <4B1D1171.1000701@redhat.com>
On Mon, Dec 07, 2009 at 03:30:09PM +0100, Gerd Hoffmann wrote:
> On 12/07/09 15:13, Michael S. Tsirkin wrote:
>> Gerd, any idea whether "one MSI-X vector" feature is worth pursuing?
>
> I'd rate it low priority. First because virtio-enabled guests can use
> virtio-net+blk. Also because with the upcoming p35 support we'll get a
> more modern pc emulation including a ioapic with all 24 IRQ lines being
> wired up, which will help reducing IRQ sharing too.
>
> MSI support (no -X) could be more intresting (for emulated devices) as
> it is older and thus support is more common. My T60 for example has no
> device with MSI-X support but 9 with MSI support. Linux turns on MSI
> for 7 of them (4 PCIe ports, e1000, ahci, iwl3945).
>
> cheers,
> Gerd
Yes, but what matters is guest support I think.
On windows it seems that both msix and msi support
were added simulataneously.
It won't be hard to add MSI support, but let's determine
when is it needed.
--
MST
prev parent reply other threads:[~2009-12-07 14:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 8:16 [Qemu-devel] [PATCH 1/2] pc: add machine type for 0.12 Gerd Hoffmann
2009-11-25 8:16 ` [Qemu-devel] [PATCH 2/2] virtio: enable msi-x for console+balloon Gerd Hoffmann
2009-12-07 9:37 ` [Qemu-devel] " Michael S. Tsirkin
2009-12-07 10:32 ` Gerd Hoffmann
2009-12-07 10:59 ` Michael S. Tsirkin
2009-12-07 11:24 ` Gerd Hoffmann
2009-12-07 13:03 ` Michael S. Tsirkin
2009-12-07 13:16 ` Gerd Hoffmann
2009-12-07 14:13 ` Michael S. Tsirkin
2009-12-07 14:30 ` Gerd Hoffmann
2009-12-07 14:43 ` Michael S. Tsirkin [this message]
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=20091207144314.GA5734@redhat.com \
--to=mst@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.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).