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 05/11] virtio: introduce legacy virtio devices
Date: Thu, 30 Oct 2014 19:02:01 +0100 [thread overview]
Message-ID: <20141030190201.41e8940d.cornelia.huck@de.ibm.com> (raw)
In-Reply-To: <20141028164018.29d73d9f@bahia.local>
On Tue, 28 Oct 2014 16:40:18 +0100
Greg Kurz <gkurz@linux.vnet.ibm.com> wrote:
> On Tue, 7 Oct 2014 16:40:01 +0200
> Cornelia Huck <cornelia.huck@de.ibm.com> wrote:
>
> > Introduce a helper function to indicate whether a virtio device is
> > operating in legacy or virtio standard mode.
> >
> > It may be used to make decisions about the endianess of virtio accesses
> > and other virtio-1 specific changes, enabling us to support transitional
> > devices.
> >
> > Reviewed-by: Thomas Huth <thuth@linux.vnet.ibm.com>
> > Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
> > ---
> > hw/virtio/virtio.c | 6 +++++-
> > include/hw/virtio/virtio-access.h | 4 ++++
> > include/hw/virtio/virtio.h | 13 +++++++++++--
> > 3 files changed, 20 insertions(+), 3 deletions(-)
> >
> > diff --git a/hw/virtio/virtio.c b/hw/virtio/virtio.c
> > index 7aaa953..e6ae3a0 100644
> > --- a/hw/virtio/virtio.c
> > +++ b/hw/virtio/virtio.c
> > @@ -883,7 +883,11 @@ static bool virtio_device_endian_needed(void *opaque)
> > VirtIODevice *vdev = opaque;
> >
> > assert(vdev->device_endian != VIRTIO_DEVICE_ENDIAN_UNKNOWN);
> > - return vdev->device_endian != virtio_default_endian();
> > + if (virtio_device_is_legacy(vdev)) {
> > + return vdev->device_endian != virtio_default_endian();
> > + }
> > + /* Devices conforming to VIRTIO 1.0 or later are always LE. */
> > + return vdev->device_endian != VIRTIO_DEVICE_ENDIAN_LITTLE;
> > }
> >
>
> Shouldn't we have some code doing the following somewhere ?
>
> if (!virtio_device_is_legacy(vdev)) {
> vdev->device_endian = VIRTIO_DEVICE_ENDIAN_LITTLE;
> }
>
> also, since virtio-1 is LE only, do we expect device_endian to
> be different from VIRTIO_DEVICE_ENDIAN_LITTLE ?
device_endian should not depend on whether the device is legacy or not.
virtio_is_big_endian always returns false for virtio-1 devices, though.
next prev parent reply other threads:[~2014-10-31 15:37 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 [this message]
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
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=20141030190201.41e8940d.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).