From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org, Christian Borntraeger <borntraeger@linux.ibm.com>
Subject: Re: [RFC PATCH] virtio: re-order vm_running and use_started checks
Date: Thu, 3 Nov 2022 12:31:15 -0400 [thread overview]
Message-ID: <20221103122827-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20221014132108.2559156-1-alex.bennee@linaro.org>
On Fri, Oct 14, 2022 at 02:21:08PM +0100, Alex Bennée wrote:
> During migration the virtio device state can be restored before we
> restart the VM. As no devices can be running while the VM is paused it
> makes sense to bail out early in that case.
>
> This returns the order introduced in:
>
> 9f6bcfd99f (hw/virtio: move vm_running check to virtio_device_started)
>
> to what virtio-sock was doing longhand.
>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> Cc: Christian Borntraeger <borntraeger@linux.ibm.com>
Still checking but this seems to cause make check to fail on Fedora 36 under ubsan.
> ---
> include/hw/virtio/virtio.h | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/include/hw/virtio/virtio.h b/include/hw/virtio/virtio.h
> index f41b4a7e64..ebb58feaac 100644
> --- a/include/hw/virtio/virtio.h
> +++ b/include/hw/virtio/virtio.h
> @@ -385,14 +385,14 @@ static inline bool virtio_is_big_endian(VirtIODevice *vdev)
>
> static inline bool virtio_device_started(VirtIODevice *vdev, uint8_t status)
> {
> - if (vdev->use_started) {
> - return vdev->started;
> - }
> -
> if (!vdev->vm_running) {
> return false;
> }
>
> + if (vdev->use_started) {
> + return vdev->started;
> + }
> +
> return status & VIRTIO_CONFIG_S_DRIVER_OK;
> }
>
> --
> 2.34.1
next prev parent reply other threads:[~2022-11-03 16:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 13:21 [RFC PATCH] virtio: re-order vm_running and use_started checks Alex Bennée
2022-10-14 13:54 ` Christian Borntraeger
2022-10-17 21:00 ` Philippe Mathieu-Daudé
2022-10-26 20:26 ` Michael S. Tsirkin
2022-11-03 16:31 ` Michael S. Tsirkin [this message]
2022-11-04 15:56 ` Michael S. Tsirkin
2022-11-04 15:59 ` Christian Borntraeger
2022-11-04 16:13 ` Michael S. Tsirkin
2022-11-04 16:14 ` Michael S. Tsirkin
2022-11-04 16:51 ` Christian Borntraeger
2022-11-04 16:58 ` Christian Borntraeger
2022-11-04 17:51 ` Michael S. Tsirkin
2022-11-04 16:31 ` Alex Bennée
2022-11-04 17:46 ` Michael S. Tsirkin
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=20221103122827-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=borntraeger@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.