From: Greg Kurz <gkurz@linux.vnet.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Cedric Le Goater <clg@fr.ibm.com>, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 0/2] vhost: support for cross endian
Date: Fri, 20 Feb 2015 11:32:53 +0100 [thread overview]
Message-ID: <20150220103253.22408.6807.stgit@bahia.local> (raw)
This patchset allows vhost_net to be used with legacy virtio when guest and
host have different endianness. It depends on the following kernel patchset:
https://lists.linuxfoundation.org/pipermail/virtualization/2015-February/029347.html
---
Cédric Le Goater (1):
vhost_net: re-enable when cross endian
Greg Kurz (1):
vhost: add VHOST_VRING_F_LEGACY_BIG_ENDIAN flag
hw/net/vhost_net.c | 19 -------------------
hw/virtio/vhost.c | 10 +++++++++-
include/hw/virtio/vhost.h | 1 +
linux-headers/linux/vhost.h | 2 ++
4 files changed, 12 insertions(+), 20 deletions(-)
--
Greg
next reply other threads:[~2015-02-20 10:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 10:32 Greg Kurz [this message]
2015-02-20 10:32 ` [Qemu-devel] [PATCH 1/2] vhost: add VHOST_VRING_F_LEGACY_BIG_ENDIAN flag Greg Kurz
2015-02-20 10:33 ` [Qemu-devel] [PATCH 2/2] vhost_net: re-enable when cross endian 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=20150220103253.22408.6807.stgit@bahia.local \
--to=gkurz@linux.vnet.ibm.com \
--cc=clg@fr.ibm.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).