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 4/5] vhost: move virtio 1.0 check to cross-endian helper
Date: Tue, 12 Jan 2016 01:23:56 +0100 [thread overview]
Message-ID: <5694479C.9070808@redhat.com> (raw)
In-Reply-To: <20160111161306.17428.37423.stgit@bahia.huguette.org>
On 11/01/2016 17:13, Greg Kurz wrote:
> Indeed vhost doesn't need to ask for vring endian fixing if the device is
> virtio 1.0, since it is already handled by the in-kernel vhost driver. This
> patch simply consolidates the logic into the existing helper.
>
> Signed-off-by: Greg Kurz <gkurz@linux.vnet.ibm.com>
> Reviewed-by: Cornelia Huck <cornelia.huck@de.ibm.com>
> ---
> hw/virtio/vhost.c | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/hw/virtio/vhost.c b/hw/virtio/vhost.c
> index 2e1e792d599e..aef750df22ad 100644
> --- a/hw/virtio/vhost.c
> +++ b/hw/virtio/vhost.c
> @@ -750,6 +750,9 @@ static void vhost_log_stop(MemoryListener *listener,
>
> static inline bool vhost_needs_vring_endian(VirtIODevice *vdev)
> {
> + if (virtio_vdev_has_feature(vdev, VIRTIO_F_VERSION_1)) {
> + return false;
> + }
> #ifdef TARGET_IS_BIENDIAN
> #ifdef HOST_WORDS_BIGENDIAN
> return !virtio_is_big_endian(vdev);
I'm wondering if in term of performance you can remove the call of
virtio_vdev_has_feature() as it is done in virtio_is_big_endian().
> @@ -811,8 +814,7 @@ static int vhost_virtqueue_start(struct vhost_dev *dev,
> return -errno;
> }
>
> - if (!virtio_vdev_has_feature(vdev, VIRTIO_F_VERSION_1) &&
> - vhost_needs_vring_endian(vdev)) {
> + if (vhost_needs_vring_endian(vdev)) {
> r = vhost_virtqueue_set_vring_endian_legacy(dev,
> virtio_is_big_endian(vdev),
> vhost_vq_index);
> @@ -908,8 +910,7 @@ static void vhost_virtqueue_stop(struct vhost_dev *dev,
> /* In the cross-endian case, we need to reset the vring endianness to
> * native as legacy devices expect so by default.
> */
> - if (!virtio_vdev_has_feature(vdev, VIRTIO_F_VERSION_1) &&
> - vhost_needs_vring_endian(vdev)) {
> + if (vhost_needs_vring_endian(vdev)) {
> r = vhost_virtqueue_set_vring_endian_legacy(dev,
> !virtio_is_big_endian(vdev),
> vhost_vq_index);
>
>
next prev parent reply other threads:[~2016-01-12 0:24 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 [this message]
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
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=5694479C.9070808@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).