From: Cedric Le Goater <clg@fr.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: kvm@vger.kernel.org, kvm-ppc@vger.kernel.org, agraf@suse.de,
paulus@samba.org, gkurz@linux.vnet.ibm.com.patch, aik@ozlabs.ru
Subject: Re: [RFC PATCH 0/4] vhost_net: support for cross endian guests
Date: Tue, 04 Nov 2014 09:07:47 +0100 [thread overview]
Message-ID: <54588953.4060309@fr.ibm.com> (raw)
In-Reply-To: <20141103162349.GB24877@redhat.com>
On 11/03/2014 05:23 PM, Michael S. Tsirkin wrote:
> On Wed, Oct 29, 2014 at 09:38:41AM +0100, Cédric Le Goater wrote:
>> This patchset adds a VHOST_VRING_F_BYTESWAP flag to inform the host
>> to byteswap data of the vring when the guest and the host have a
>> different endian order. The flag is stored at initialization in an
>> attribute of the virtio queues. It is then used to byteswap, or not,
>> the vring indexes and descriptors shared with the guest OS.
>>
>> The last patch adds the byteswapping of the virtio_net header as it
>> is done in qemu.
>
> Hi Cedric,
>
> Thanks for submitting this.
> One general problem with this approach, is that
> it adds overhead e.g. for x86 on x86 unconditionally.
Yes but it should be possible to #ifdef most of the routines to
make them transparent for x86.
> I will in a couple of days post a patch adding virtio 1.0
> support for vhost.
>
> This will serve as a better basis for cross-endian support in
> vhost, on top.
ok. I will rework the patchset on top of it then.
> I'll try to remember to Cc you.
Thanks.
C.
>> The patches apply on linux-3.18-rc2 and the tests were done on PowerPC
>> using the following hosts :
>>
>> fedora21/ppc64, utopic/ppc64le
>>
>> with various guests :
>>
>> trusty/ppc64le, utopic/ppc64le, debian/ppc64le,
>> rhel6.5/ppc64, fedora21/ppc64, debian/ppc64
>>
>> Regressions tests for x86_64 were done a debian host using rhel6.6,
>> fedora20 and debian guests.
>>
>>
>> Cédric Le Goater (4):
>> vhost: add VHOST_VRING_F_BYTESWAP flag
>> vhost: add byteswap routines
>> vhost: byteswap virtqueue attributes
>> vhost_net: byteswap virtio_net header
>>
>> drivers/vhost/net.c | 39 +++++++++---
>> drivers/vhost/vhost.c | 150 ++++++++++++++++++++++++++++++++++++++++----
>> drivers/vhost/vhost.h | 1 +
>> include/uapi/linux/vhost.h | 3 +
>> 4 files changed, 171 insertions(+), 22 deletions(-)
>>
>> --
>> 1.7.10.4
>
prev parent reply other threads:[~2014-11-04 8:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 8:38 [RFC PATCH 0/4] vhost_net: support for cross endian guests Cédric Le Goater
2014-10-29 8:38 ` [RFC PATCH 1/4] vhost: add VHOST_VRING_F_BYTESWAP flag Cédric Le Goater
2014-11-03 16:28 ` Michael S. Tsirkin
2014-10-29 8:38 ` [RFC PATCH 2/4] vhost: add byteswap routines Cédric Le Goater
2014-11-03 15:38 ` Cornelia Huck
2014-10-29 8:38 ` [RFC PATCH 3/4] vhost: byteswap virtqueue attributes Cédric Le Goater
2014-11-03 16:02 ` Cornelia Huck
2014-10-29 8:38 ` [RFC PATCH 4/4] vhost_net: byteswap virtio_net header Cédric Le Goater
2014-11-03 16:25 ` Michael S. Tsirkin
2014-11-03 16:23 ` [RFC PATCH 0/4] vhost_net: support for cross endian guests Michael S. Tsirkin
2014-11-04 8:07 ` Cedric Le Goater [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=54588953.4060309@fr.ibm.com \
--to=clg@fr.ibm.com \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=gkurz@linux.vnet.ibm.com.patch \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=paulus@samba.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