qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>, qemu-devel@nongnu.org
Cc: slp@redhat.com, mst@redhat.com, marcandre.lureau@redhat.com,
	stefanha@redhat.com, mathieu.poirier@linaro.org,
	viresh.kumar@linaro.org, sgarzare@redhat.com,
	Laurent Vivier <lvivier@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v4 1/5] tests/qtests: override "force-legacy" for gpio virtio-mmio tests
Date: Wed, 30 Nov 2022 13:15:05 +0100	[thread overview]
Message-ID: <8b1853f5-8f93-0cac-4753-94e1f49066a7@redhat.com> (raw)
In-Reply-To: <20221130112439.2527228-2-alex.bennee@linaro.org>

On 30/11/2022 12.24, Alex Bennée wrote:
> The GPIO device is a VIRTIO_F_VERSION_1 devices but running with a
> legacy MMIO interface we miss out that feature bit causing confusion.
> For the GPIO test force the mmio bus to support non-legacy so we can
> properly test it.
> 
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
> Resolves: https://gitlab.com/qemu-project/qemu/-/issues/1333
> ---
>   tests/qtest/libqos/virtio-gpio.c | 3 ++-
>   1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/tests/qtest/libqos/virtio-gpio.c b/tests/qtest/libqos/virtio-gpio.c
> index 762aa6695b..f22d7b5eb5 100644
> --- a/tests/qtest/libqos/virtio-gpio.c
> +++ b/tests/qtest/libqos/virtio-gpio.c
> @@ -154,7 +154,8 @@ static void virtio_gpio_register_nodes(void)
>       QOSGraphEdgeOptions edge_opts = { };
>   
>       /* vhost-user-gpio-device */
> -    edge_opts.extra_device_opts = "id=gpio0,chardev=chr-vhost-user-test";
> +    edge_opts.extra_device_opts = "id=gpio0,chardev=chr-vhost-user-test "
> +        "-global virtio-mmio.force-legacy=false";
>       qos_node_create_driver("vhost-user-gpio-device",
>                               virtio_gpio_device_create);
>       qos_node_consumes("vhost-user-gpio-device", "virtio-bus", &edge_opts);

Acked-by: Thomas Huth <thuth@redhat.com>



  reply	other threads:[~2022-11-30 12:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-30 11:24 [PATCH for 7.2 v4 0/5] final vhost-user fixes Alex Bennée
2022-11-30 11:24 ` [PATCH v4 1/5] tests/qtests: override "force-legacy" for gpio virtio-mmio tests Alex Bennée
2022-11-30 12:15   ` Thomas Huth [this message]
2022-11-30 11:24 ` [PATCH v4 2/5] vhost: enable vrings in vhost_dev_start() for vhost-user devices Alex Bennée
2022-11-30 11:24 ` [PATCH v4 3/5] hw/virtio: add started_vu status field to vhost-user-gpio Alex Bennée
2022-11-30 11:24 ` [PATCH v4 4/5] hw/virtio: generalise CHR_EVENT_CLOSED handling Alex Bennée
2022-11-30 21:21   ` Stefan Hajnoczi
2022-12-01 17:05     ` Alex Bennée
2022-12-01  6:56   ` Michael S. Tsirkin
2022-11-30 11:24 ` [PATCH v4 5/5] include/hw: VM state takes precedence in virtio_device_should_start Alex Bennée

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=8b1853f5-8f93-0cac-4753-94e1f49066a7@redhat.com \
    --to=thuth@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=lvivier@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=mathieu.poirier@linaro.org \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sgarzare@redhat.com \
    --cc=slp@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=viresh.kumar@linaro.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).