From: "Michael S. Tsirkin" <mst@redhat.com>
To: qemu-devel@nongnu.org
Cc: Krishna Kumar <krkumar2@in.ibm.com>,
Carsten Otte <cotte@de.ibm.com>,
lguest@lists.ozlabs.org, Shirley Ma <xma@us.ibm.com>,
kvm@vger.kernel.org, linux-s390@vger.kernel.org,
habanero@linux.vnet.ibm.com,
Rusty Russell <rusty@rustcorp.com.au>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
virtualization@lists.linux-foundation.org, steved@us.ibm.com,
Christian Borntraeger <borntraeger@de.ibm.com>,
Tom Lendacky <tahm@linux.vnet.ibm.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
linux390@de.ibm.com
Subject: [Qemu-devel] [PATCHv2 0/2] virtio-net: 64 bit features, event index
Date: Fri, 20 May 2011 02:24:00 +0300 [thread overview]
Message-ID: <cover.1305846929.git.mst@redhat.com> (raw)
OK, here's a patch that implements the virtio spec update that I
sent earlier. It supercedes the PUBLISH_USED_IDX patches
I sent out earlier.
Support is added in both userspace and vhost-net.
If you see issues or are just curious, you can
turn the new feature off. For example:
-global virtio-net-pci.event_idx=on
-global virtio-blk-pci.event_idx=off
Also, it's possible to try both vhost-net and virtio-net.
Another part is adding support for 64 bit features in
place. The high bits are actually unused, to test
hack qemu to set some high bit.
linux code is here:
git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost-net-next-event-idx-v3
git://git.kernel.org/pub/scm/linux/kernel/git/mst/qemu-kvm.git virtio-net-event-idx-v3
Changes from v1:
- unify used and avail ring handling in a single feature bit
- copy avail event idx fix from vhost-net
Michael S. Tsirkin (2):
virtio/vhost: support 64 bit features
virtio+vhost: event idx feature
hw/qdev-properties.c | 39 +++++++++++++---
hw/qdev.h | 10 ++++
hw/s390-virtio-bus.c | 5 +-
hw/s390-virtio-bus.h | 2 +-
hw/syborg_virtio.c | 7 ++-
hw/vhost_net.c | 14 ++++--
hw/vhost_net.h | 4 +-
hw/virtio-9p.c | 2 +-
hw/virtio-balloon.c | 2 +-
hw/virtio-blk.c | 2 +-
hw/virtio-blk.h | 2 +-
hw/virtio-net.c | 11 +++--
hw/virtio-net.h | 34 +++++++-------
hw/virtio-pci.c | 91 +++++++++++++++++++++++++++----------
hw/virtio-serial-bus.c | 2 +-
hw/virtio.c | 116 ++++++++++++++++++++++++++++++++++++++++++------
hw/virtio.h | 24 +++++++---
17 files changed, 275 insertions(+), 92 deletions(-)
--
1.7.5.53.gc233e
next reply other threads:[~2011-05-19 23:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-19 23:24 Michael S. Tsirkin [this message]
2011-05-19 23:24 ` [Qemu-devel] [PATCHv2 1/2] virtio/vhost: support 64 bit features Michael S. Tsirkin
2011-05-19 23:24 ` [Qemu-devel] [PATCHv2 2/2] virtio+vhost: event idx feature 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=cover.1305846929.git.mst@redhat.com \
--to=mst@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cotte@de.ibm.com \
--cc=habanero@linux.vnet.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=krkumar2@in.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=lguest@lists.ozlabs.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux390@de.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=rusty@rustcorp.com.au \
--cc=schwidefsky@de.ibm.com \
--cc=steved@us.ibm.com \
--cc=tahm@linux.vnet.ibm.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=xma@us.ibm.com \
/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).