qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kurz <gkurz@linux.vnet.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>,
	Laurent Vivier <lvivier@redhat.com>,
	qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH v4 0/6] virtio/vhost cross-endian cleanup
Date: Fri, 05 Feb 2016 11:39:27 +0100	[thread overview]
Message-ID: <20160205103927.21017.26364.stgit@bahia.huguette.org> (raw)

This series brings some improvements to the cross-endian support in the
virtio and vhost code:
- use qemu_set_vnet_be() and qemu_set_vnet_le() directly from virtio-net,
  so that backend cross-endian capabilities benefit to both emulated and
  vhost accelerated devices
- optimize virtio_access_is_big_endian() for little-endian targets
- various cleanups

This v4 is a respin of the v3, taking into account the following fix:

commit cf0a628f6e81bfc9b7a944fa0b80c3594836df56
Author: Laurent Vivier <lvivier@redhat.com>
Date:   Wed Jan 13 20:26:25 2016 +0100

    net: set endianness on all backend devices

It impacts patches 1 and 2, that had already been reviewed.

Laurent, Cornelia,

Could you please ack/nack the changes ?

The series is based on Michael Tsirkin's tree:

git://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git pci

Thanks.

--
Greg

---

Greg Kurz (6):
      virtio-net: use the backend cross-endian capabilities
      vhost-net: revert support of cross-endian vnet headers
      virtio: move cross-endian helper to vhost
      vhost: move virtio 1.0 check to cross-endian helper
      vhost: simplify vhost_needs_vring_endian()
      virtio: optimize virtio_access_is_big_endian() for little-endian targets


 hw/net/vhost_net.c                |   41 +++-------------------
 hw/net/virtio-net.c               |   68 ++++++++++++++++++++++++++++++++++++-
 hw/virtio/vhost.c                 |   27 +++++++++++++--
 include/hw/virtio/virtio-access.h |   28 ++-------------
 include/hw/virtio/virtio-net.h    |    1 +
 5 files changed, 98 insertions(+), 67 deletions(-)

             reply	other threads:[~2016-02-05 10:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-05 10:39 Greg Kurz [this message]
2016-02-05 10:43 ` [Qemu-devel] [PATCH v4 1/6] virtio-net: use the backend cross-endian capabilities Greg Kurz
2016-02-05 11:33   ` Cornelia Huck
2016-02-05 15:41     ` Greg Kurz
2016-02-05 10:45 ` [Qemu-devel] [PATCH v4 2/6] vhost-net: revert support of cross-endian vnet headers Greg Kurz
2016-02-05 10:45 ` [Qemu-devel] [PATCH v4 3/6] virtio: move cross-endian helper to vhost Greg Kurz
2016-02-05 10:45 ` [Qemu-devel] [PATCH v4 4/6] vhost: move virtio 1.0 check to cross-endian helper Greg Kurz
2016-02-05 13:06   ` Laurent Vivier
2016-02-05 10:46 ` [Qemu-devel] [PATCH v4 5/6] vhost: simplify vhost_needs_vring_endian() Greg Kurz
2016-02-05 11:39   ` Cornelia Huck
2016-02-05 13:02   ` Laurent Vivier
2016-02-05 10:46 ` [Qemu-devel] [PATCH v4 6/6] virtio: optimize virtio_access_is_big_endian() for little-endian targets Greg Kurz
2016-02-05 13:07 ` [Qemu-devel] [PATCH v4 0/6] virtio/vhost cross-endian cleanup Laurent Vivier
2016-02-10 10:22 ` Laurent Vivier
2016-02-16  9:57   ` Greg Kurz
2016-02-16 10:04     ` Michael S. Tsirkin
2016-02-16 10:07       ` Greg Kurz

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=20160205103927.21017.26364.stgit@bahia.huguette.org \
    --to=gkurz@linux.vnet.ibm.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=lvivier@redhat.com \
    --cc=mst@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).