virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kurz <gkurz@linux.vnet.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Cedric Le Goater <clg@fr.ibm.com>,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	virtualization@lists.linux-foundation.org
Subject: Re: [PATCH 0/3] vhost_net: support for cross endian guests
Date: Mon, 23 Feb 2015 14:24:47 +0100	[thread overview]
Message-ID: <20150223142447.23b0572a@bahia.local> (raw)
In-Reply-To: <20150222095351.GD17529@redhat.com>

On Sun, 22 Feb 2015 10:53:51 +0100
"Michael S. Tsirkin" <mst@redhat.com> wrote:
> On Fri, Feb 20, 2015 at 11:07:24AM +0100, Greg Kurz wrote:
> > Hi,
> > 
> > This patchset allows vhost_net to be used with legacy virtio
> > when guest and host have a different endianness. It is based
> > on previous work by Cédric Le Goater:
> > 
> > https://www.mail-archive.com/kvm-ppc@vger.kernel.org/msg09848.html
> > 
> > As suggested by MST:
> > - the API now asks for a specific format (big endian) instead of the hint
> >   whether byteswap is needed or not (patch 1)
> > - rebased on top of the virtio-1 accessors (patch 2)
> > 
> > Patch 3 is a separate fix: I think it is also valid for virtio-1.
> 
> I don't think so. See e.g. this code in tun:
>                         gso.csum_offset = cpu_to_tun16(tun, skb->csum_offset);
> looks like it has the correct endian-ness for virtio-1.
> 
> 

Indeed. I will fix tun/macvtap as you suggested.

Thanks for the review.

--
Greg

> 
> > Please comment.
> > 
> > ---
> > 
> > Greg Kurz (3):
> >       vhost: add VHOST_VRING_F_LEGACY_BIG_ENDIAN flag
> >       vhost: add support for legacy virtio
> >       vhost_net: fix virtio_net header endianness
> > 
> > 
> >  drivers/vhost/net.c        |   32 ++++++++++++++++++++++++++------
> >  drivers/vhost/vhost.c      |    6 +++++-
> >  drivers/vhost/vhost.h      |   23 +++++++++++++++++------
> >  include/uapi/linux/vhost.h |    2 ++
> >  4 files changed, 50 insertions(+), 13 deletions(-)
> > 
> > --
> > Greg
> 

_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

  reply	other threads:[~2015-02-23 13:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150220100724.18608.74654.stgit@bahia.local>
2015-02-20 10:07 ` [PATCH 1/3] vhost: add VHOST_VRING_F_LEGACY_BIG_ENDIAN flag Greg Kurz
2015-02-22  9:51   ` Michael S. Tsirkin
2015-02-20 10:14 ` [PATCH 2/3] vhost: add support for legacy virtio Greg Kurz
2015-02-20 10:15 ` [PATCH 3/3] vhost_net: fix virtio_net header endianness Greg Kurz
     [not found] ` <20150220101454.18608.64016.stgit@bahia.local>
2015-02-22  9:46   ` Michael S. Tsirkin
     [not found] ` <20150220100746.18608.15083.stgit@bahia.local>
2015-02-22  9:48   ` [PATCH 2/3] vhost: add support for legacy virtio Michael S. Tsirkin
2015-02-22  9:53 ` [PATCH 0/3] vhost_net: support for cross endian guests Michael S. Tsirkin
2015-02-23 13:24   ` Greg Kurz [this message]
2015-02-20 10:07 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=20150223142447.23b0572a@bahia.local \
    --to=gkurz@linux.vnet.ibm.com \
    --cc=clg@fr.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=virtualization@lists.linux-foundation.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).