From: "Michael S. Tsirkin" <mst@redhat.com>
To: Greg Kurz <gkurz@linux.vnet.ibm.com>
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>,
Thomas Huth <thuth@redhat.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
Jason Wang <jasowang@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/6] vhost: cross-endian support
Date: Wed, 17 Jun 2015 17:10:50 +0200 [thread overview]
Message-ID: <20150617171037-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <20150617132323.6560.29432.stgit@bahia.lab.toulouse-stg.fr.ibm.com>
On Wed, Jun 17, 2015 at 03:23:24PM +0200, Greg Kurz wrote:
> Hi,
>
> This series brings initial enablement in vhost to support legacy virtio
> devices when host and guest have different endianness (for example, ppc64
> versus ppc64le).
>
> Only vhost_net is fully enabled at the moment... I haven't looked at
> vhost_scsi yet.
>
> It is basically the same patch set I had sent last month:
>
> https://lists.gnu.org/archive/html/qemu-devel/2015-05/msg00780.html
>
> ... without the "virtio: relax feature check" patch since QEMU now
> supports 64-bit features.
>
> Some kernel support is needed, already available in Michael's vhost-next
> branch at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git
>
> Please review.
Seems minor enough, I've applied this.
> ---
>
> Cédric Le Goater (1):
> vhost_net: re-enable when cross endian
>
> Greg Kurz (5):
> linux-headers: sync vhost.h
> virtio: introduce virtio_legacy_is_cross_endian()
> vhost: set vring endianness for legacy virtio
> tap: add VNET_LE/VNET_BE operations
> vhost-net: tell tap backend about the vnet endianness
>
>
> hw/net/vhost_net.c | 50 +++++++++++++++++++++++--------------
> hw/virtio/vhost.c | 50 ++++++++++++++++++++++++++++++++++++-
> include/hw/virtio/virtio-access.h | 13 ++++++++++
> include/net/net.h | 6 ++++
> linux-headers/linux/vhost.h | 14 ++++++++++
> net/net.c | 18 +++++++++++++
> net/tap-linux.c | 34 +++++++++++++++++++++++++
> net/tap-linux.h | 2 +
> net/tap.c | 16 ++++++++++++
> net/tap_int.h | 2 +
> 10 files changed, 185 insertions(+), 20 deletions(-)
>
> --
> Greg
prev parent reply other threads:[~2015-06-17 15:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 13:23 [Qemu-devel] [PATCH 0/6] vhost: cross-endian support Greg Kurz
2015-06-17 13:23 ` [Qemu-devel] [PATCH 1/6] linux-headers: sync vhost.h Greg Kurz
2015-06-17 13:23 ` [Qemu-devel] [PATCH 2/6] virtio: introduce virtio_legacy_is_cross_endian() Greg Kurz
2015-06-17 13:23 ` [Qemu-devel] [PATCH 3/6] vhost: set vring endianness for legacy virtio Greg Kurz
2015-06-17 13:23 ` [Qemu-devel] [PATCH 4/6] tap: add VNET_LE/VNET_BE operations Greg Kurz
2015-06-17 13:23 ` [Qemu-devel] [PATCH 5/6] vhost-net: tell tap backend about the vnet endianness Greg Kurz
2015-06-19 9:16 ` Thomas Huth
2015-06-19 9:45 ` Greg Kurz
2015-06-17 13:23 ` [Qemu-devel] [PATCH 6/6] vhost_net: re-enable when cross endian Greg Kurz
2015-06-17 15:10 ` 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=20150617171037-mutt-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=cornelia.huck@de.ibm.com \
--cc=gkurz@linux.vnet.ibm.com \
--cc=jasowang@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.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).