From: "Michael S. Tsirkin" <mst@redhat.com>
To: Rusty Russell <rusty@rustcorp.com.au>,
virtualization@lists.linux-foundation.org,
Anthony Liguori <anthony@codemonkey.ws>,
kvm@vger.kernel.org, avi@redhat.com
Subject: [PATCH RFC 0/8] virtio: add guest MSI-X support
Date: Mon, 27 Apr 2009 15:31:36 +0300 [thread overview]
Message-ID: <20090427123136.GA1152@redhat.com> (raw)
Add optional MSI-X support: use a vector per virtqueue with
fallback to a common vector and finally to regular interrupt.
Teach all drivers to use it.
I added 2 new virtio operations: request_vqs/free_vqs because MSI
needs to know the total number of vectors upfront.
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
---
Here's a draft set of patches for MSI-X support in the guest. It still
needs to be tested properly, and performance impact measured, but I
thought I'd share it here in the hope of getting some very early
feedback/flames.
Michael S. Tsirkin (8):
virtio: add request_vqs/free_vqs virtio operations
virtio_blk: add request_vqs/free_vqs calls
virtio-rng: add request_vqs/free_vqs calls
virtio_console: add request_vqs/free_vqs calls
virtio_net: add request_vqs/free_vqs calls
virtio_balloon: add request_vqs/free_vqs calls
virtio_pci: split up vp_interrupt
virtio_pci: optional MSI-X support
drivers/block/virtio_blk.c | 9 ++-
drivers/char/hw_random/virtio-rng.c | 10 ++-
drivers/char/virtio_console.c | 8 ++-
drivers/net/virtio_net.c | 16 +++-
drivers/virtio/virtio_balloon.c | 9 ++-
drivers/virtio/virtio_pci.c | 192 ++++++++++++++++++++++++++++++-----
include/linux/virtio_config.h | 35 +++++++
7 files changed, 247 insertions(+), 32 deletions(-)
next reply other threads:[~2009-04-27 12:33 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 12:31 Michael S. Tsirkin [this message]
2009-04-27 14:00 ` [PATCH RFC 0/8] virtio: add guest MSI-X support Christian Borntraeger
2009-04-27 14:32 ` Michael S. Tsirkin
2009-04-27 14:32 ` Michael S. Tsirkin
2009-04-27 15:37 ` Christian Borntraeger
2009-04-27 17:17 ` Michael S. Tsirkin
2009-04-27 17:17 ` Michael S. Tsirkin
2009-04-27 15:37 ` Christian Borntraeger
2009-04-27 15:06 ` Avi Kivity
2009-04-27 15:39 ` Michael S. Tsirkin
2009-04-27 16:59 ` Christian Borntraeger
2009-04-27 17:19 ` Michael S. Tsirkin
2009-04-27 17:19 ` Michael S. Tsirkin
2009-04-27 16:59 ` Christian Borntraeger
2009-04-28 6:47 ` Avi Kivity
2009-04-28 17:41 ` Michael S. Tsirkin
2009-04-28 17:41 ` Michael S. Tsirkin
2009-04-28 17:51 ` Avi Kivity
2009-04-28 18:02 ` Michael S. Tsirkin
2009-04-28 19:56 ` Anthony Liguori
2009-04-28 19:56 ` Anthony Liguori
2009-04-28 21:01 ` Michael S. Tsirkin
2009-05-04 9:21 ` Avi Kivity
2009-05-04 11:54 ` Michael S. Tsirkin
2009-05-04 11:54 ` Michael S. Tsirkin
2009-05-04 11:57 ` Avi Kivity
2009-05-04 11:57 ` Avi Kivity
2009-05-04 9:21 ` Avi Kivity
2009-04-28 18:02 ` Michael S. Tsirkin
2009-04-28 17:51 ` Avi Kivity
2009-04-28 6:47 ` Avi Kivity
2009-04-27 15:39 ` Michael S. Tsirkin
2009-04-27 14:00 ` Christian Borntraeger
2009-04-27 14:39 ` Anthony Liguori
2009-04-27 14:39 ` Anthony Liguori
2009-04-27 17:42 ` Michael S. Tsirkin
2009-04-27 17:42 ` Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2009-04-27 12:31 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=20090427123136.GA1152@redhat.com \
--to=mst@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.