qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Marcel Apfelbaum <marcel@redhat.com>
Cc: jasowang@redhat.com, famz@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH V2 2/2] tests/vhost-user: check vhost-user feature negotiation
Date: Thu, 30 Jul 2015 09:47:50 +0300	[thread overview]
Message-ID: <20150730094719-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <1438200409-27381-3-git-send-email-marcel@redhat.com>

On Wed, Jul 29, 2015 at 11:06:49PM +0300, Marcel Apfelbaum wrote:
> Check the backend receives all declared virtio features
> that are also supported by QEMU virtio.
> 
> Signed-off-by: Marcel Apfelbaum <marcel@redhat.com>
> ---
>  tests/vhost-user-test.c | 19 ++++++++++++++++---
>  1 file changed, 16 insertions(+), 3 deletions(-)
> 
> diff --git a/tests/vhost-user-test.c b/tests/vhost-user-test.c
> index 228acb6..019b880 100644
> --- a/tests/vhost-user-test.c
> +++ b/tests/vhost-user-test.c
> @@ -17,6 +17,7 @@
>  #include "sysemu/sysemu.h"
>  
>  #include <linux/vhost.h>
> +#include <linux/virtio_net.h>
>  #include <sys/mman.h>
>  #include <sys/vfs.h>
>  #include <qemu/sockets.h>
> @@ -297,14 +298,26 @@ static void chr_read(void *opaque, const uint8_t *buf, int size)
>          /* send back features to qemu */
>          msg.flags |= VHOST_USER_REPLY_MASK;
>          msg.size = sizeof(m.u64);
> -        msg.u64 = 0x1ULL << VHOST_USER_F_PROTOCOL_FEATURES;
> +        msg.u64 = (0x1ULL << VHOST_USER_F_PROTOCOL_FEATURES) |
> +                  (0x1ULL << VIRTIO_F_ANY_LAYOUT) |
> +                  (0x1ULL << VIRTIO_F_VERSION_1)  |
> +                  (0x1ULL << VIRTIO_NET_F_MRG_RXBUF) |
> +                  (0x1ULL << VIRTIO_NET_F_MQ);
>          p = (uint8_t *) &msg;
>          qemu_chr_fe_write_all(chr, p, VHOST_USER_HDR_SIZE + msg.size);
>          break;
>  

No, this mixes protocol features and virtio features.
It's not what was intended.

>      case VHOST_USER_SET_FEATURES:
> -	g_assert_cmpint(msg.u64 & (0x1ULL << VHOST_USER_F_PROTOCOL_FEATURES),
> -			!=, 0ULL);
> +        g_assert_cmpint(msg.u64 & (0x1ULL << VHOST_USER_F_PROTOCOL_FEATURES),
> +            !=, 0ULL);
> +        g_assert_cmpint(msg.u64 & (0x1ULL << VIRTIO_F_ANY_LAYOUT),
> +            !=, 0ULL);
> +        g_assert_cmpint(msg.u64 & (0x1ULL << VIRTIO_F_VERSION_1),
> +            !=, 0ULL);
> +        g_assert_cmpint(msg.u64 & (0x1ULL << VIRTIO_NET_F_MRG_RXBUF),
> +            !=, 0ULL);
> +        g_assert_cmpint(msg.u64 & (0x1ULL << VIRTIO_NET_F_MQ),
> +            !=, 0ULL);
>          break;
>  
>      case VHOST_USER_GET_PROTOCOL_FEATURES:
> -- 
> 2.1.0

  reply	other threads:[~2015-07-30  6:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-29 20:06 [Qemu-devel] [PATCH V2 0/2] vhost-user: sync backend Marcel Apfelbaum
2015-07-29 20:06 ` [Qemu-devel] [PATCH V2 1/2] vhost-user: sync backend features Marcel Apfelbaum
2015-07-30  6:47   ` Michael S. Tsirkin
2015-07-30  7:27     ` Marcel Apfelbaum
2015-07-29 20:06 ` [Qemu-devel] [PATCH V2 2/2] tests/vhost-user: check vhost-user feature negotiation Marcel Apfelbaum
2015-07-30  6:47   ` Michael S. Tsirkin [this message]
2015-07-30  7:30     ` Marcel Apfelbaum

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=20150730094719-mutt-send-email-mst@redhat.com \
    --to=mst@redhat.com \
    --cc=famz@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=marcel@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).