[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150423152608.11795.4373.stgit@bahia.local>
Date: Thu, 23 Apr 2015 17:26:08 +0200
From: Greg Kurz <gkurz@...ux.vnet.ibm.com>
To: Rusty Russell <rusty@...tcorp.com.au>,
"Michael S. Tsirkin" <mst@...hat.com>
Cc: Cornelia Huck <cornelia.huck@...ibm.com>,
linux-api@...r.kernel.org, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org, virtualization@...ts.linux-foundation.org
Subject: [PATCH v5 0/8] vhost: support for cross endian guests
Hi,
This patchset allows vhost to be used with legacy virtio when guest and host
have a different endianness. It is compatible with modern virtio and can be
fully compiled out through kernel config.
FWIW, I could flawlessly kexec/reboot guests from ppc64 to ppc64le and back.
I could also migrate from a ppc64 to a ppc64le host and back. No regressions
on x86 as expected. My experimental QEMU tree is here:
https://github.com/gkurz/qemu.git vhost/cross-endian
I'd be glad if this series could make it to 4.1.
Cheers.
---
Greg Kurz (8):
virtio: introduce virtio_is_little_endian() helper
tun: add tun_is_little_endian() helper
macvtap: introduce macvtap_is_little_endian() helper
vringh: introduce vringh_is_little_endian() helper
vhost: introduce vhost_is_little_endian() helper
virtio: add explicit big-endian support to memory accessors
vhost: cross-endian support for legacy devices
macvtap/tun: cross-endian support for little-endian hosts
drivers/net/Kconfig | 14 ++++++
drivers/net/macvtap.c | 68 +++++++++++++++++++++++++++++-
drivers/net/tun.c | 70 ++++++++++++++++++++++++++++++-
drivers/vhost/Kconfig | 15 +++++++
drivers/vhost/vhost.c | 86 ++++++++++++++++++++++++++++++++++++++
drivers/vhost/vhost.h | 25 ++++++++---
include/linux/virtio_byteorder.h | 24 ++++++-----
include/linux/virtio_config.h | 20 ++++++---
include/linux/vringh.h | 17 +++++---
include/uapi/linux/if_tun.h | 6 +++
include/uapi/linux/vhost.h | 12 +++++
11 files changed, 324 insertions(+), 33 deletions(-)
--
Greg
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists