From: Greg Kurz <gkurz@linux.vnet.ibm.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: thuth@linux.vnet.ibm.com, kvm@vger.kernel.org, mst@redhat.com,
rusty@rustcorp.com.au, qemu-devel@nongnu.org,
virtualization@lists.linux-foundation.org
Subject: Re: [Qemu-devel] [PATCH RFC v3 05/12] virtio: introduce legacy virtio devices
Date: Wed, 26 Nov 2014 19:46:38 +0100 [thread overview]
Message-ID: <20141126194638.2e110e78@bahia.local> (raw)
In-Reply-To: <1417022923-1654-6-git-send-email-cornelia.huck@de.ibm.com>
On Wed, 26 Nov 2014 18:28:36 +0100
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 2eb5d3c..4149f45 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;
> }
>
Sorry but I still don't understand why we need to stream the device_endian
subsection if we have a virtio-1 device... this field is only used on
legacy device paths. Can you share an example where it is needed ?
> static const VMStateDescription vmstate_virtio_device_endian = {
> diff --git a/include/hw/virtio/virtio-access.h b/include/hw/virtio/virtio-access.h
> index 46456fd..c123ee0 100644
> --- a/include/hw/virtio/virtio-access.h
> +++ b/include/hw/virtio/virtio-access.h
> @@ -19,6 +19,10 @@
>
> static inline bool virtio_access_is_big_endian(VirtIODevice *vdev)
> {
> + if (!virtio_device_is_legacy(vdev)) {
> + /* Devices conforming to VIRTIO 1.0 or later are always LE. */
> + return false;
> + }
> #if defined(TARGET_IS_BIENDIAN)
> return virtio_is_big_endian(vdev);
> #elif defined(TARGET_WORDS_BIGENDIAN)
> diff --git a/include/hw/virtio/virtio.h b/include/hw/virtio/virtio.h
> index b408166..40e567c 100644
> --- a/include/hw/virtio/virtio.h
> +++ b/include/hw/virtio/virtio.h
> @@ -275,9 +275,18 @@ void virtio_queue_set_host_notifier_fd_handler(VirtQueue *vq, bool assign,
> void virtio_queue_notify_vq(VirtQueue *vq);
> void virtio_irq(VirtQueue *vq);
>
> +static inline bool virtio_device_is_legacy(VirtIODevice *vdev)
> +{
> + return !(vdev->guest_features[1] & (1 << (VIRTIO_F_VERSION_1 - 32)));
> +}
> +
> static inline bool virtio_is_big_endian(VirtIODevice *vdev)
> {
> - assert(vdev->device_endian != VIRTIO_DEVICE_ENDIAN_UNKNOWN);
> - return vdev->device_endian == VIRTIO_DEVICE_ENDIAN_BIG;
> + if (virtio_device_is_legacy(vdev)) {
> + assert(vdev->device_endian != VIRTIO_DEVICE_ENDIAN_UNKNOWN);
> + return vdev->device_endian == VIRTIO_DEVICE_ENDIAN_BIG;
> + }
> + /* Devices conforming to VIRTIO 1.0 or later are always LE. */
> + return false;
> }
> #endif
next prev parent reply other threads:[~2014-11-26 18:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 17:28 [Qemu-devel] [PATCH RFC v3 00/12] qemu: towards virtio-1 host support Cornelia Huck
2014-11-26 17:28 ` [Qemu-devel] [PATCH RFC v3 01/12] linux-headers/virtio_config: Update with VIRTIO_F_VERSION_1 Cornelia Huck
2014-11-26 17:28 ` [Qemu-devel] [PATCH RFC v3 02/12] virtio: cull virtio_bus_set_vdev_features Cornelia Huck
2014-11-26 17:28 ` [Qemu-devel] [PATCH RFC v3 03/12] virtio: support more feature bits Cornelia Huck
2014-11-26 17:28 ` [Qemu-devel] [PATCH RFC v3 04/12] s390x/virtio-ccw: fix check for WRITE_FEAT Cornelia Huck
2014-11-26 17:28 ` [Qemu-devel] [PATCH RFC v3 05/12] virtio: introduce legacy virtio devices Cornelia Huck
2014-11-26 18:46 ` Greg Kurz [this message]
2014-11-26 18:51 ` Michael S. Tsirkin
2014-11-26 17:28 ` [Qemu-devel] [PATCH RFC v3 06/12] virtio: allow virtio-1 queue layout Cornelia Huck
2014-11-26 17:28 ` [Qemu-devel] [PATCH RFC v3 07/12] dataplane: allow virtio-1 devices Cornelia Huck
2014-11-26 18:15 ` Greg Kurz
2014-11-26 17:28 ` [Qemu-devel] [PATCH RFC v3 08/12] s390x/css: Add a callback for when subchannel gets disabled Cornelia Huck
2014-11-26 17:28 ` [Qemu-devel] [PATCH RFC v3 09/12] s390x/virtio-ccw: add virtio set-revision call Cornelia Huck
2014-11-26 17:28 ` [Qemu-devel] [PATCH RFC v3 10/12] s390x/virtio-ccw: support virtio-1 set_vq format Cornelia Huck
2014-11-26 17:28 ` [Qemu-devel] [PATCH RFC v3 11/12] virtio-net/virtio-blk: enable virtio 1.0 Cornelia Huck
2014-11-26 18:50 ` Michael S. Tsirkin
2014-11-27 10:34 ` Cornelia Huck
2014-11-26 17:28 ` [Qemu-devel] [PATCH RFC v3 12/12] s390x/virtio-ccw: " 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=20141126194638.2e110e78@bahia.local \
--to=gkurz@linux.vnet.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--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).