From: Vasyl Vavrychuk <vvavrychuk@gmail.com>
To: Sergio Lopez <slp@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3] virtio-mmio: implement modern (v2), personality (virtio-1)
Date: Sat, 21 Sep 2019 10:06:04 +0300 [thread overview]
Message-ID: <a51cbe82-9213-d535-a43b-57f68f78475d@gmail.com> (raw)
In-Reply-To: <20190913120559.40835-1-slp@redhat.com>
Hi, Sergio,
> For this reason, the v2 personality is disabled, keeping the legacy
> behavior as default. Machine types willing to use v2, can enable it
> using MachineClass's compat_props.
...
> + DEFINE_PROP_BOOL("force-legacy", VirtIOMMIOProxy, legacy, true),
Currently, I am not enable to set "force-legacy" to false from command
line for
virt machine.
I think, the "force-legacy" and compat_props should work the other way
around.
The "force-legacy" should be set to false by default to select a new
behaviour.
Instead of this hw_compat_4_1 should be modified to keep the old behaviour:
--- a/hw/core/machine.c
+++ b/hw/core/machine.c
@@ -29,6 +29,7 @@
GlobalProperty hw_compat_4_1[] = {
{ "virtio-pci", "x-pcie-flr-init", "off" },
+ { "virtio-mmio", "force-legacy", "on" },
};
const size_t hw_compat_4_1_len = G_N_ELEMENTS(hw_compat_4_1);
This way, one can keep the old behaviour by doing "-M virt-4.1"
Best regards,
Vasyl
next prev parent reply other threads:[~2019-09-21 13:11 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 15:10 [Qemu-devel] [PULL 00/10] virtio, vhost, pc: features, fixes, cleanups Michael S. Tsirkin
2019-08-01 0:40 ` [Qemu-devel] [PATCH v2] docs/nvdimm: add example on persistent backend setup Wei Yang
2019-08-01 8:05 ` Stefan Hajnoczi
2019-09-11 8:51 ` Wei Yang
2019-09-12 12:16 ` Stefan Hajnoczi
2019-09-12 21:44 ` Wei Yang
2019-09-17 15:10 ` [Qemu-devel] [PULL 02/10] " Michael S. Tsirkin
2019-08-21 12:16 ` [Qemu-devel] [PATCH v3] virtio pmem: user document Pankaj Gupta
2019-08-26 12:46 ` Cornelia Huck
2019-09-16 6:30 ` Pankaj Gupta
2019-09-17 15:11 ` [Qemu-devel] [PULL 09/10] " Michael S. Tsirkin
2019-08-22 18:34 ` [Qemu-devel] [PATCH 1/2] vhost-user-blk: prevent using uninitialized vqs Raphael Norwitz
2019-08-22 18:34 ` [Qemu-devel] [PATCH 2/2] backends/vhost-user.c: " Raphael Norwitz
2019-08-28 8:29 ` Stefan Hajnoczi
2019-09-17 15:10 ` [Qemu-devel] [PULL 04/10] " Michael S. Tsirkin
2019-08-23 3:43 ` [Qemu-devel] [Qemu-block] [PATCH 1/2] vhost-user-blk: " yuchenlin via Qemu-devel
2019-08-28 8:28 ` [Qemu-devel] " Stefan Hajnoczi
2019-09-17 15:10 ` [Qemu-devel] [PULL 03/10] " Michael S. Tsirkin
2019-09-10 14:03 ` [Qemu-devel] [PATCH v2] MAINTAINERS: update virtio-rng and virtio-serial maintainer Laurent Vivier
2019-09-17 15:10 ` [Qemu-devel] [PULL 01/10] " Michael S. Tsirkin
2019-09-13 12:06 ` [Qemu-devel] [PATCH v3] virtio-mmio: implement modern (v2) personality (virtio-1) Sergio Lopez
2019-09-16 14:40 ` Cornelia Huck
2019-09-17 15:11 ` [Qemu-devel] [PULL 10/10] " Michael S. Tsirkin
2019-09-21 7:06 ` Vasyl Vavrychuk [this message]
2019-09-23 13:58 ` [Qemu-devel] [PATCH v3] virtio-mmio: implement modern (v2), " Sergio Lopez
2019-09-19 10:13 ` [Qemu-devel] [PULL 00/10] virtio, vhost, pc: features, fixes, cleanups Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2019-09-16 8:07 [Qemu-devel] [PATCH v3 0/4] intel_iommu: Do sanity check of vfio-pci earlier Peter Xu
2019-09-16 8:07 ` [Qemu-devel] [PATCH v3 1/4] intel_iommu: Sanity check vfio-pci config on machine init done Peter Xu
2019-09-17 15:10 ` [Qemu-devel] [PULL 05/10] " Michael S. Tsirkin
2019-09-16 8:07 ` [Qemu-devel] [PATCH v3 2/4] qdev/machine: Introduce hotplug_allowed hook Peter Xu
2019-09-17 15:10 ` [Qemu-devel] [PULL 06/10] " Michael S. Tsirkin
2019-09-16 8:07 ` [Qemu-devel] [PATCH v3 3/4] pc/q35: Disallow vfio-pci hotplug without VT-d caching mode Peter Xu
2019-09-17 15:11 ` [Qemu-devel] [PULL 07/10] " Michael S. Tsirkin
2019-09-16 8:07 ` [Qemu-devel] [PATCH v3 4/4] intel_iommu: Remove the caching-mode check during flag change Peter Xu
2019-09-17 15:11 ` [Qemu-devel] [PULL 08/10] " 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=a51cbe82-9213-d535-a43b-57f68f78475d@gmail.com \
--to=vvavrychuk@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=slp@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).