From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: Greg Kurz <gkurz@linux.vnet.ibm.com>
Cc: thuth@linux.vnet.ibm.com, rusty@rustcorp.com.au,
qemu-devel@nongnu.org, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [Qemu-devel] [PATCH RFC 07/11] dataplane: allow virtio-1 devices
Date: Thu, 30 Oct 2014 10:18:38 +0100 [thread overview]
Message-ID: <20141030101838.2ddee2dc.cornelia.huck@de.ibm.com> (raw)
In-Reply-To: <20141028162254.2a4f2cf4@bahia.local>
On Tue, 28 Oct 2014 16:22:54 +0100
Greg Kurz <gkurz@linux.vnet.ibm.com> wrote:
> On Tue, 7 Oct 2014 16:40:03 +0200
> Cornelia Huck <cornelia.huck@de.ibm.com> wrote:
>
> > Handle endianness conversion for virtio-1 virtqueues correctly.
> >
> > Note that dataplane now needs to be built per-target.
> >
>
> It also affects hw/virtio/virtio-pci.c:
>
> In file included from include/hw/virtio/dataplane/vring.h:23:0,
> from include/hw/virtio/virtio-scsi.h:21,
> from hw/virtio/virtio-pci.c:24:
> include/hw/virtio/virtio-access.h: In function ‘virtio_access_is_big_endian’:
> include/hw/virtio/virtio-access.h:28:15: error: attempt to use poisoned "TARGET_WORDS_BIGENDIAN"
> #elif defined(TARGET_WORDS_BIGENDIAN)
> ^
>
> FWIW when I added endian ambivalent support to virtio, I remember *some people*
> getting angry at the idea of turning common code into per-target... :)
Well, it probably can't be helped for something that is
endian-sensitive like virtio :( (Although we should try to keep it as
local as possible.)
>
> See comment below.
>
> > Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
> > ---
> > hw/block/dataplane/virtio-blk.c | 3 +-
> > hw/scsi/virtio-scsi-dataplane.c | 2 +-
> > hw/virtio/Makefile.objs | 2 +-
> > hw/virtio/dataplane/Makefile.objs | 2 +-
> > hw/virtio/dataplane/vring.c | 85 +++++++++++++++++++----------------
> > include/hw/virtio/dataplane/vring.h | 64 ++++++++++++++++++++++++--
> > 6 files changed, 113 insertions(+), 45 deletions(-)
> >
> > diff --git a/include/hw/virtio/dataplane/vring.h b/include/hw/virtio/dataplane/vring.h
> > index d3e086a..fde15f3 100644
> > --- a/
> > +++ b/include/hw/virtio/dataplane/vring.h
> > @@ -20,6 +20,7 @@
> > #include "qemu-common.h"
> > #include "hw/virtio/virtio_ring.h"
> > #include "hw/virtio/virtio.h"
> > +#include "hw/virtio/virtio-access.h"
> >
>
> Since the following commit:
>
> commit 244e2898b7a7735b3da114c120abe206af56a167
> Author: Fam Zheng <famz@redhat.com>
> Date: Wed Sep 24 15:21:41 2014 +0800
>
> virtio-scsi: Add VirtIOSCSIVring in VirtIOSCSIReq
>
> The include/hw/virtio/dataplane/vring.h header is indirectly included
> by hw/virtio/virtio-pci.c. Why don't you move all this target dependent
> helpers to another header ?
Ah, this seems to have come in after I hacked on that code - I'll take a
look at splitting off the accessors.
next prev parent reply other threads:[~2014-10-30 9:19 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 14:39 [Qemu-devel] [PATCH RFC 00/11] qemu: towards virtio-1 host support Cornelia Huck
2014-10-07 14:39 ` [Qemu-devel] [PATCH RFC 01/11] linux-headers/virtio_config: Update with VIRTIO_F_VERSION_1 Cornelia Huck
2014-10-07 14:39 ` [Qemu-devel] [PATCH RFC 02/11] virtio: cull virtio_bus_set_vdev_features Cornelia Huck
2014-10-07 14:39 ` [Qemu-devel] [PATCH RFC 03/11] virtio: support more feature bits Cornelia Huck
2014-10-13 5:53 ` Rusty Russell
2014-10-13 10:55 ` Cornelia Huck
2014-10-07 14:40 ` [Qemu-devel] [PATCH RFC 04/11] s390x/virtio-ccw: fix check for WRITE_FEAT Cornelia Huck
2014-10-07 14:40 ` [Qemu-devel] [PATCH RFC 05/11] virtio: introduce legacy virtio devices Cornelia Huck
2014-10-28 15:40 ` Greg Kurz
2014-10-30 18:02 ` Cornelia Huck
2014-10-30 22:29 ` Greg Kurz
2014-11-03 11:44 ` Cornelia Huck
2014-10-07 14:40 ` [Qemu-devel] [PATCH RFC 06/11] virtio: allow virtio-1 queue layout Cornelia Huck
2014-10-07 14:40 ` [Qemu-devel] [PATCH RFC 07/11] dataplane: allow virtio-1 devices Cornelia Huck
2014-10-28 15:22 ` Greg Kurz
2014-10-30 9:18 ` Cornelia Huck [this message]
2014-10-07 14:40 ` [Qemu-devel] [PATCH RFC 08/11] s390x/css: Add a callback for when subchannel gets disabled Cornelia Huck
2014-10-07 14:40 ` [Qemu-devel] [PATCH RFC 09/11] s390x/virtio-ccw: add virtio set-revision call Cornelia Huck
2014-10-07 14:40 ` [Qemu-devel] [PATCH RFC 10/11] s390x/virtio-ccw: support virtio-1 set_vq format Cornelia Huck
2014-10-07 14:40 ` [Qemu-devel] [PATCH RFC 11/11] s390x/virtio-ccw: enable virtio 1.0 Cornelia Huck
2014-10-08 1:24 ` [Qemu-devel] [PATCH RFC 00/11] qemu: towards virtio-1 host support Andy Lutomirski
2014-10-08 9:04 ` Cornelia Huck
2014-10-22 8:44 ` Michael S. Tsirkin
2014-10-22 14:17 ` Jan Kiszka
2014-10-22 14:36 ` Michael S. Tsirkin
2014-10-22 20:34 ` Benjamin Herrenschmidt
2014-10-23 6:44 ` Jan Kiszka
2014-10-23 9:18 ` Michael S. Tsirkin
2014-10-23 7:12 ` Michael S. Tsirkin
2014-10-23 21:42 ` Michael S. Tsirkin
2014-10-24 8:38 ` Cornelia Huck
2014-10-24 12:37 ` Cornelia Huck
2014-10-24 14:05 ` Michael S. Tsirkin
2014-10-24 14:17 ` Michael S. Tsirkin
2014-10-28 4:43 ` Michael S. Tsirkin
2014-10-30 16:52 ` Cornelia Huck
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=20141030101838.2ddee2dc.cornelia.huck@de.ibm.com \
--to=cornelia.huck@de.ibm.com \
--cc=gkurz@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=rusty@rustcorp.com.au \
--cc=thuth@linux.vnet.ibm.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).