From: Cornelia Huck <cohuck@redhat.com>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>, Qinghua Cheng <qcheng@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-stable@nongnu.org, David Hildenbrand <david@redhat.com>,
qemu-devel@nongnu.org,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Halil Pasic <pasic@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
qemu-s390x@nongnu.org, Richard Henderson <rth@twiddle.net>,
Qian Cai <caiqian@redhat.com>
Subject: Re: [PATCH v3 1/4] virtio: skip legacy support check on machine types less than 5.1
Date: Fri, 18 Sep 2020 11:13:42 +0200 [thread overview]
Message-ID: <20200918111342.01fd51c0.cohuck@redhat.com> (raw)
In-Reply-To: <20200918074710.27810-2-sgarzare@redhat.com>
On Fri, 18 Sep 2020 09:47:07 +0200
Stefano Garzarella <sgarzare@redhat.com> wrote:
> Commit 9b3a35ec82 ("virtio: verify that legacy support is not accidentally
> on") added a check that returns an error if legacy support is on, but the
> device is not legacy.
s/is not legacy/does not support legacy/ ?
>
> Unfortunately some devices were wrongly declared legacy even if they
s/legacy/legacy capable/ ?
> were not (e.g vhost-vsock).
>
> To avoid migration issues, we add a virtio-device property
> (x-disable-legacy-check) to skip the legacy error, printing a warning
> instaed, for machine types < 5.1.
s/instaed/instead/
>
> Cc: qemu-stable@nongnu.org
> Fixes: 9b3a35ec82 ("virtio: verify that legacy support is not accidentally on")
> Suggested-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> Suggested-by: Cornelia Huck <cohuck@redhat.com>
> Signed-off-by: Stefano Garzarella <sgarzare@redhat.com>
> ---
> v3:
> - added virtio_legacy_check_disabled() helper
> - moved warning where error was returned [Cornelia]
> v2:
> - fixed Cornelia's e-mail address
> ---
> include/hw/virtio/virtio.h | 2 ++
> hw/core/machine.c | 1 +
> hw/s390x/virtio-ccw.c | 15 ++++++++++++---
> hw/virtio/virtio-pci.c | 14 ++++++++++++--
> hw/virtio/virtio.c | 7 +++++++
> 5 files changed, 34 insertions(+), 5 deletions(-)
>
> diff --git a/include/hw/virtio/virtio.h b/include/hw/virtio/virtio.h
> index 807280451b..f90cfb03e3 100644
> --- a/include/hw/virtio/virtio.h
> +++ b/include/hw/virtio/virtio.h
> @@ -103,6 +103,7 @@ struct VirtIODevice
> bool use_started;
> bool started;
> bool start_on_kick; /* when virtio 1.0 feature has not been negotiated */
> + bool disable_legacy_check;
> VMChangeStateEntry *vmstate;
> char *bus_name;
> uint8_t device_endian;
> @@ -396,5 +397,6 @@ static inline bool virtio_device_disabled(VirtIODevice *vdev)
> }
>
> bool virtio_legacy_allowed(VirtIODevice *vdev);
> +bool virtio_legacy_check_disabled(VirtIODevice *vdev);
>
> #endif
> diff --git a/hw/core/machine.c b/hw/core/machine.c
> index ea26d61237..b686eab798 100644
> --- a/hw/core/machine.c
> +++ b/hw/core/machine.c
> @@ -44,6 +44,7 @@ GlobalProperty hw_compat_5_0[] = {
> { "vmport", "x-signal-unsupported-cmd", "off" },
> { "vmport", "x-report-vmx-type", "off" },
> { "vmport", "x-cmds-v2", "off" },
> + { "virtio-device", "x-disable-legacy-check", "true" },
> };
> const size_t hw_compat_5_0_len = G_N_ELEMENTS(hw_compat_5_0);
>
> diff --git a/hw/s390x/virtio-ccw.c b/hw/s390x/virtio-ccw.c
> index 8feb3451a0..97a01bc48a 100644
> --- a/hw/s390x/virtio-ccw.c
> +++ b/hw/s390x/virtio-ccw.c
> @@ -1122,9 +1122,18 @@ static void virtio_ccw_device_plugged(DeviceState *d, Error **errp)
> }
>
> if (!virtio_ccw_rev_max(dev) && !virtio_legacy_allowed(vdev)) {
> - error_setg(errp, "Invalid value of property max_rev "
> - "(is %d expected >= 1)", virtio_ccw_rev_max(dev));
> - return;
> + /*
> + * To avoid migration issues, we allow legacy mode when legacy
> + * check is disabled in the old machine types (< 5.1).
> + */
> + if (virtio_legacy_check_disabled(vdev)) {
> + warn_report("device is modern-only, but for backward "
> + "compatibility legacy is allowed");
Hm...
"device requires revision >= 1, but for backward compatibility
max_rev=0 is allowed"
seems more appropriate.
(I think I need to rethink the checking for ccw anyway.)
> + } else {
> + error_setg(errp, "Invalid value of property max_rev "
> + "(is %d expected >= 1)", virtio_ccw_rev_max(dev));
> + return;
> + }
> }
>
> if (virtio_get_num_queues(vdev) > VIRTIO_QUEUE_MAX) {
(...)
With the message for ccw changed,
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
next prev parent reply other threads:[~2020-09-18 9:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 7:47 [PATCH v3 0/4] vhost-vsock: force virtio version 1 Stefano Garzarella
2020-09-18 7:47 ` [PATCH v3 1/4] virtio: skip legacy support check on machine types less than 5.1 Stefano Garzarella
2020-09-18 9:13 ` Cornelia Huck [this message]
2020-09-18 9:35 ` Stefano Garzarella
2020-09-18 7:47 ` [PATCH v3 2/4] vhost-vsock-pci: force virtio version 1 Stefano Garzarella
2020-09-18 9:19 ` Cornelia Huck
2020-09-18 10:00 ` Stefano Garzarella
2020-09-18 7:47 ` [PATCH v3 3/4] vhost-user-vsock-pci: " Stefano Garzarella
2020-09-18 9:23 ` Cornelia Huck
2020-09-18 10:01 ` Stefano Garzarella
2020-09-18 7:47 ` [PATCH v3 4/4] vhost-vsock-ccw: " Stefano Garzarella
2020-09-18 9:24 ` Cornelia Huck
2020-09-18 8:00 ` [PATCH v3 0/4] vhost-vsock: " no-reply
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=20200918111342.01fd51c0.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=caiqian@redhat.com \
--cc=david@redhat.com \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=qcheng@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=rth@twiddle.net \
--cc=sgarzare@redhat.com \
--cc=thuth@redhat.com \
/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).