From: Laurent Vivier <lvivier@redhat.com>
To: Greg Kurz <gkurz@linux.vnet.ibm.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 5/5] virtio: optimize virtio_access_is_big_endian() for little-endian targets
Date: Tue, 12 Jan 2016 01:33:47 +0100 [thread overview]
Message-ID: <569449EB.9070108@redhat.com> (raw)
In-Reply-To: <20160111161317.17428.44013.stgit@bahia.huguette.org>
On 11/01/2016 17:18, Greg Kurz wrote:
> When adding cross-endian support, we introduced the TARGET_IS_BIENDIAN macro
> and the virtio_access_is_big_endian() helper to have a branchless fast path
> in the virtio memory accessors for targets that don't switch endian.
>
> This was considered as a strong requirement at the time.
>
> Now we have added a runtime check for virtio 1.0, which ruins the benefit
> of the virtio_access_is_big_endian() helper for always little-endian targets.
>
> With this patch, always little-endian targets stop checking for virtio 1.0,
> since the result is little-endian in all cases.
>
> Signed-off-by: Greg Kurz <gkurz@linux.vnet.ibm.com>
> ---
> v2:
> - simplified the logic as suggested by Laurent Vivier
> ---
> include/hw/virtio/virtio-access.h | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/include/hw/virtio/virtio-access.h b/include/hw/virtio/virtio-access.h
> index f1f12afe9089..8dc84f520316 100644
> --- a/include/hw/virtio/virtio-access.h
> +++ b/include/hw/virtio/virtio-access.h
> @@ -19,13 +19,13 @@
>
> static inline bool virtio_access_is_big_endian(VirtIODevice *vdev)
> {
> +#if defined(TARGET_IS_BIENDIAN)
> + return virtio_is_big_endian(vdev);
> +#elif defined(TARGET_WORDS_BIGENDIAN)
> if (virtio_vdev_has_feature(vdev, VIRTIO_F_VERSION_1)) {
> /* 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)
> return true;
> #else
> return false;
>
>
Reviewed-by: Laurent Vivier <lvivier@redhat.com>
prev parent reply other threads:[~2016-01-12 0:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 16:11 [Qemu-devel] [PATCH v2 0/5] virtio/vhost cross-endian cleanup Greg Kurz
2016-01-11 16:12 ` [Qemu-devel] [PATCH v2 1/5] virtio-net: use the backend cross-endian capabilities Greg Kurz
2016-01-11 18:16 ` Cornelia Huck
2016-01-12 0:32 ` Laurent Vivier
2016-01-12 17:24 ` Laurent Vivier
2016-01-13 9:06 ` Greg Kurz
2016-01-13 9:53 ` Laurent Vivier
2016-01-13 10:18 ` Greg Kurz
2016-01-11 16:12 ` [Qemu-devel] [PATCH v2 2/5] Revert "vhost-net: tell tap backend about the vnet endianness" Greg Kurz
2016-01-12 0:32 ` Laurent Vivier
2016-01-11 16:13 ` [Qemu-devel] [PATCH v2 3/5] virtio: move cross-endian helper to vhost Greg Kurz
2016-01-12 0:33 ` Laurent Vivier
2016-01-11 16:13 ` [Qemu-devel] [PATCH v2 4/5] vhost: move virtio 1.0 check to cross-endian helper Greg Kurz
2016-01-12 0:23 ` Laurent Vivier
2016-01-12 10:12 ` Greg Kurz
2016-01-11 16:18 ` [Qemu-devel] [PATCH v2 5/5] virtio: optimize virtio_access_is_big_endian() for little-endian targets Greg Kurz
2016-01-11 18:18 ` Cornelia Huck
2016-01-12 0:33 ` Laurent Vivier [this message]
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=569449EB.9070108@redhat.com \
--to=lvivier@redhat.com \
--cc=gkurz@linux.vnet.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).