search for: tun_vnet_b

...; > diff --git a/drivers/net/Kconfig b/drivers/net/Kconfig > index df51d60..f0e23a0 100644 > --- a/drivers/net/Kconfig > +++ b/drivers/net/Kconfig > @@ -244,6 +244,18 @@ config TUN > > If you don't know what to use this for, you don't need it. > > +config TUN_VNET_BE > + bool "Support for big-endian vnet headers" > + default n > + ---help--- > + This option allows TUN/TAP and MACVTAP device drivers to parse > + vnet headers that are in big-endian byte order. It is useful > + when the headers come from a big-endian legacy virti...

...; > diff --git a/drivers/net/Kconfig b/drivers/net/Kconfig > index df51d60..f0e23a0 100644 > --- a/drivers/net/Kconfig > +++ b/drivers/net/Kconfig > @@ -244,6 +244,18 @@ config TUN > > If you don't know what to use this for, you don't need it. > > +config TUN_VNET_BE > + bool "Support for big-endian vnet headers" > + default n > + ---help--- > + This option allows TUN/TAP and MACVTAP device drivers to parse > + vnet headers that are in big-endian byte order. It is useful > + when the headers come from a big-endian legacy virti...

...les changed, 134 insertions(+), 2 deletions(-) diff --git a/drivers/net/Kconfig b/drivers/net/Kconfig index df51d60..f0e23a0 100644 --- a/drivers/net/Kconfig +++ b/drivers/net/Kconfig @@ -244,6 +244,18 @@ config TUN If you don't know what to use this for, you don't need it. +config TUN_VNET_BE + bool "Support for big-endian vnet headers" + default n + ---help--- + This option allows TUN/TAP and MACVTAP device drivers to parse + vnet headers that are in big-endian byte order. It is useful + when the headers come from a big-endian legacy virtio driver and + the host is l...

...b/drivers/net/Kconfig > > index df51d60..f0e23a0 100644 > > --- a/drivers/net/Kconfig > > +++ b/drivers/net/Kconfig > > @@ -244,6 +244,18 @@ config TUN > > > > If you don't know what to use this for, you don't need it. > > > > +config TUN_VNET_BE > > + bool "Support for big-endian vnet headers" > > + default n > > + ---help--- > > + This option allows TUN/TAP and MACVTAP device drivers to parse > > + vnet headers that are in big-endian byte order. It is useful > > + when the headers come...

...N_F_TSO6 | diff --git a/drivers/net/tun.c b/drivers/net/tun.c index 7c4f6b6..9fa05d6 100644 --- a/drivers/net/tun.c +++ b/drivers/net/tun.c @@ -111,6 +111,7 @@ do { \ #define TUN_FASYNC IFF_ATTACH_QUEUE /* High bits in flags field are unused. */ #define TUN_VNET_LE 0x80000000 +#define TUN_VNET_BE 0x40000000 #define TUN_FEATURES (IFF_NO_PI | IFF_ONE_QUEUE | IFF_VNET_HDR | \ IFF_MULTI_QUEUE) @@ -206,10 +207,58 @@ struct tun_struct { u32 flow_count; }; +#ifdef CONFIG_TUN_VNET_CROSS_LE +static inline bool tun_legacy_is_little_endian(struct tun_struct *tun) +{ + return tun-...

Hi, This patchset allows vhost to be used with legacy virtio when guest and host have a different endianness. Patch 7 got rewritten according to Cornelia's and Michael's comments. I have also introduced patch 8 that brings BE vnet headers support to tun/macvtap. This series is enough to have vhost_net working flawlessly. I could succesfully reboot guests from ppc64 to ppc64le and

Hi, This patchset allows vhost to be used with legacy virtio when guest and host have a different endianness. Patch 7 got rewritten according to Cornelia's and Michael's comments. I have also introduced patch 8 that brings BE vnet headers support to tun/macvtap. This series is enough to have vhost_net working flawlessly. I could succesfully reboot guests from ppc64 to ppc64le and

...dex df51d60..f0e23a0 100644 > > > --- a/drivers/net/Kconfig > > > +++ b/drivers/net/Kconfig > > > @@ -244,6 +244,18 @@ config TUN > > > > > > If you don't know what to use this for, you don't need it. > > > > > > +config TUN_VNET_BE > > > + bool "Support for big-endian vnet headers" > > > + default n > > > + ---help--- > > > + This option allows TUN/TAP and MACVTAP device drivers to parse > > > + vnet headers that are in big-endian byte order. It is useful > > &...

...dex df51d60..f0e23a0 100644 > > > --- a/drivers/net/Kconfig > > > +++ b/drivers/net/Kconfig > > > @@ -244,6 +244,18 @@ config TUN > > > > > > If you don't know what to use this for, you don't need it. > > > > > > +config TUN_VNET_BE > > > + bool "Support for big-endian vnet headers" > > > + default n > > > + ---help--- > > > + This option allows TUN/TAP and MACVTAP device drivers to parse > > > + vnet headers that are in big-endian byte order. It is useful > > &...

...t; > > --- a/drivers/net/Kconfig > > > > +++ b/drivers/net/Kconfig > > > > @@ -244,6 +244,18 @@ config TUN > > > > > > > > If you don't know what to use this for, you don't need it. > > > > > > > > +config TUN_VNET_BE > > > > + bool "Support for big-endian vnet headers" > > > > + default n > > > > + ---help--- > > > > + This option allows TUN/TAP and MACVTAP device drivers to parse > > > > + vnet headers that are in big-endian byte order....

Only cosmetic and documentation changes since v5. --- 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

Only cosmetic and documentation changes since v5. --- 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

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

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