From: Greg Kurz <gkurz@linux.vnet.ibm.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/6] Revert "vhost-net: tell tap backend about the vnet endianness"
Date: Fri, 8 Jan 2016 11:26:05 +0100 [thread overview]
Message-ID: <20160108112605.73a81c13@bahia.local> (raw)
In-Reply-To: <20160108111120.3429b210.cornelia.huck@de.ibm.com>
On Fri, 8 Jan 2016 11:11:20 +0100
Cornelia Huck <cornelia.huck@de.ibm.com> wrote:
> On Thu, 07 Jan 2016 12:32:08 +0100
> Greg Kurz <gkurz@linux.vnet.ibm.com> wrote:
>
> > This reverts commit 5be7d9f1b1452613b95c6ba70b8d7ad3d0797991.
> >
> > Cross-endian is now configured by the core virtio-net code. We simply
> > fall back on full emulation if the net backend cannot support the
> > requested endianness for vnet headers.
> >
> > Signed-off-by: Greg Kurz <gkurz@linux.vnet.ibm.com>
> > ---
> > hw/net/vhost_net.c | 33 +--------------------------------
> > hw/net/virtio-net.c | 7 +++++++
> > 2 files changed, 8 insertions(+), 32 deletions(-)
>
> > diff --git a/hw/net/virtio-net.c b/hw/net/virtio-net.c
> > index d4cc94ea5e55..5a0ab6ad5bb5 100644
> > --- a/hw/net/virtio-net.c
> > +++ b/hw/net/virtio-net.c
> > @@ -128,6 +128,13 @@ static void virtio_net_vhost_status(VirtIONet *n, uint8_t status)
> > if (!n->vhost_started) {
> > int r, i;
> >
> > + if (n->needs_vnet_hdr_swap) {
> > + error_report("backend does not support %s vnet headers."
>
> s/./;/
>
I'll fix that.
> > + "falling back on userspace virtio",
>
> s/on/to/
>
> ?
>
I thought the same but...
http://idioms.thefreedictionary.com/fall+back+on
> > + virtio_is_big_endian(vdev) ? "BE" : "LE");
> > + return;
> > + }
> > +
> > /* Any packets outstanding? Purge them to avoid touching rings
> > * when vhost is running.
> > */
> >
> >
>
next prev parent reply other threads:[~2016-01-08 10:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 11:31 [Qemu-devel] [PATCH 0/6] virtio/vhost cross-endian cleanup Greg Kurz
2016-01-07 11:32 ` [Qemu-devel] [PATCH 1/6] virtio-net: use the backend cross-endian capabilities Greg Kurz
2016-01-07 16:22 ` Laurent Vivier
2016-01-07 17:23 ` Greg Kurz
2016-01-07 18:32 ` Laurent Vivier
2016-01-08 14:19 ` Greg Kurz
2016-01-08 15:25 ` Laurent Vivier
2016-01-08 16:00 ` Greg Kurz
2016-01-07 11:32 ` [Qemu-devel] [PATCH 2/6] Revert "vhost-net: tell tap backend about the vnet endianness" Greg Kurz
2016-01-07 19:52 ` Laurent Vivier
2016-01-08 9:07 ` Greg Kurz
2016-01-08 10:11 ` Cornelia Huck
2016-01-08 10:26 ` Greg Kurz [this message]
2016-01-08 11:09 ` Cornelia Huck
2016-01-07 11:32 ` [Qemu-devel] [PATCH 3/6] virtio: drop the virtio_needs_swap() helper Greg Kurz
2016-01-07 19:55 ` Laurent Vivier
2016-01-08 9:16 ` Greg Kurz
2016-01-07 11:32 ` [Qemu-devel] [PATCH 4/6] virtio: move cross-endian helper to vhost Greg Kurz
2016-01-07 11:32 ` [Qemu-devel] [PATCH 5/6] vhost: move virtio 1.0 check to cross-endian helper Greg Kurz
2016-01-07 20:07 ` Laurent Vivier
2016-01-08 9:21 ` Greg Kurz
2016-01-08 10:07 ` Cornelia Huck
2016-01-08 10:22 ` Laurent Vivier
2016-01-07 11:32 ` [Qemu-devel] [PATCH 6/6] virtio: optimize virtio_access_is_big_endian() for little-endian targets Greg Kurz
2016-01-07 20:25 ` Laurent Vivier
2016-01-08 9:27 ` 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=20160108112605.73a81c13@bahia.local \
--to=gkurz@linux.vnet.ibm.com \
--cc=cornelia.huck@de.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).