From: Greg Kurz <gkurz@linux.vnet.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 0/3] virtio: cross-endian helpers fixes
Date: Tue, 5 Jan 2016 20:19:22 +0100 [thread overview]
Message-ID: <20160105201922.2b265b0c@bahia.local> (raw)
In-Reply-To: <20151223172823.3601f342@bahia.local>
On Wed, 23 Dec 2015 17:28:23 +0100
Greg Kurz <gkurz@linux.vnet.ibm.com> wrote:
> On Wed, 23 Dec 2015 15:47:00 +0200
> "Michael S. Tsirkin" <mst@redhat.com> wrote:
>
> > On Thu, Dec 17, 2015 at 09:52:46AM +0100, Greg Kurz wrote:
> > > This series tries to rework cross-endian helpers for better clarity.
> > > It does not change behaviour, except perhaps patch 3/3 even if I could not
> > > measure any performance gain.
> >
> > Breaks build:
> >
> > CC mips64-softmmu/hw/mips/mips_malta.o
> > /home/mst/scm/qemu/hw/net/vhost_net.c: In function
> > ‘vhost_net_set_vnet_endian’:
> > /home/mst/scm/qemu/hw/net/vhost_net.c:208:10: error: implicit
> > declaration of function ‘virtio_legacy_is_cross_endian’
> > [-Werror=implicit-function-declaration]
> > (virtio_legacy_is_cross_endian(dev) &&
> > !virtio_is_big_endian(dev))) {
> > ^
> > /home/mst/scm/qemu/hw/net/vhost_net.c:208:9: error: nested extern
> > declaration of ‘virtio_legacy_is_cross_endian’ [-Werror=nested-externs]
> > (virtio_legacy_is_cross_endian(dev) &&
> > !virtio_is_big_endian(dev))) {
> > ^
> > cc1: all warnings being treated as errors
> > /home/mst/scm/qemu/rules.mak:57: recipe for target 'hw/net/vhost_net.o'
> > failed
> > make[1]: *** [hw/net/vhost_net.o] Error 1
> > Makefile:186: recipe for target 'subdir-i386-softmmu' failed
> > make: *** [subdir-i386-softmmu] Error 2
> >
> >
> > please always build all architectures.
> >
>
> Ok. I'll do so from now on.
>
The break isn't architecture related actually. It is because this series
depends on the "virtio-net/vhost-net: share cross-endian enablement" series
I had posted before... my bad. Since most of these series is cleanup of the
cross-endian code, I'll repost a single series with all the patches.
> > > ---
> > >
> > > Greg Kurz (3):
> > > virtio: move cross-endian helper to vhost
> > > vhost: move virtio 1.0 check to cross-endian helper
> > > virtio: optimize virtio_access_is_big_endian() for little-endian targets
> > >
> > >
> > > hw/virtio/vhost.c | 22 ++++++++++++++++++----
> > > include/hw/virtio/virtio-access.h | 16 +++-------------
> > > 2 files changed, 21 insertions(+), 17 deletions(-)
> >
>
>
next prev parent reply other threads:[~2016-01-05 19:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 8:52 [Qemu-devel] [PATCH v2 0/3] virtio: cross-endian helpers fixes Greg Kurz
2015-12-17 8:52 ` [Qemu-devel] [PATCH v2 1/3] virtio: move cross-endian helper to vhost Greg Kurz
2015-12-17 8:53 ` [Qemu-devel] [PATCH v2 2/3] vhost: move virtio 1.0 check to cross-endian helper Greg Kurz
2015-12-17 8:55 ` [Qemu-devel] [PATCH v2 3/3] virtio: optimize virtio_access_is_big_endian() for little-endian targets Greg Kurz
2015-12-23 13:47 ` [Qemu-devel] [PATCH v2 0/3] virtio: cross-endian helpers fixes Michael S. Tsirkin
2015-12-23 16:28 ` Greg Kurz
2016-01-05 19:19 ` Greg Kurz [this message]
2016-01-06 11:09 ` Michael S. Tsirkin
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=20160105201922.2b265b0c@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).