From: Greg Kurz <groug@kaod.org>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-stable@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-2.8] qdev: apply global properties in reverse order
Date: Mon, 5 Dec 2016 20:11:56 +0100 [thread overview]
Message-ID: <20161205201156.46b0116b@bahia> (raw)
In-Reply-To: <20161205164200.49bec0f6.cornelia.huck@de.ibm.com>
On Mon, 5 Dec 2016 16:42:00 +0100
Cornelia Huck <cornelia.huck@de.ibm.com> wrote:
> On Mon, 05 Dec 2016 16:21:22 +0100
> Greg Kurz <groug@kaod.org> wrote:
>
> > The current code recursively applies global properties from child up to
> > parent. So, if you have:
> >
> > -global virtio-pci.disable-modern=on
> > -global virtio-blk-pci.disable-modern=off
> >
> > Then the default value of disable-modern for a virtio-blk-pci device is on,
> > which looks wrong from an OOP perspective.
> >
> > This patch reverses the logic, so that a child property always prevail.
>
> This sounds reasonable...
>
> >
> > This fixes a subtle bug that got introduced in 2.7 with commit "9a4c0e220d8a
> > hw/virtio-pci: fix virtio behaviour" for older (< 2.7) machine types: the
> > HW_COMPAT_2_6 macro contains global virtio-pci.disable-* properties which
> > would silently override global properties passed on the command line for
> > virtio subtypes.
> >
> > Signed-off-by: Greg Kurz <groug@kaod.org>
> > ---
> >
> > AFAIK, libvirt's XML doesn't know about modern/legacy modes for virtio
> > devices. Early adopters of virtio 1.0 had to rely on the <qemu:commandline>
> > tag to pass global properties to QEMU. This patch ensures that XML files
> > used with older machine types remain valid with newer versions of QEMU.
> >
> > FWIW I guess it could help to have this fix in 2.8, and also probably in
> > 2.7.1.
>
> ...but I'm a bit worried about doing that change this late in the
> cycle, as we may introduce subtle changes for other configurations. At
> the very least, we should look over the existing backwards compat
> properties (I'll look at those I'm familiar with).
>
Yeah, it's unfortunate I encountered the issue this late... I usually
pass properties to -device directly. :-\ Maybe we should set global
options per virtio-pci subtype as you suggested on IRC ?
Note: sorry for the late answer but I've just received all the mails...
> >
> > Please advise.
> >
> > hw/core/qdev-properties.c | 11 ++++++++++-
> > 1 file changed, 10 insertions(+), 1 deletion(-)
> >
> > diff --git a/hw/core/qdev-properties.c b/hw/core/qdev-properties.c
> > index 2a8276806721..1345f489d6b1 100644
> > --- a/hw/core/qdev-properties.c
> > +++ b/hw/core/qdev-properties.c
> > @@ -1119,11 +1119,20 @@ static void qdev_prop_set_globals_for_type(DeviceState *dev,
> > void qdev_prop_set_globals(DeviceState *dev)
> > {
> > ObjectClass *class = object_get_class(OBJECT(dev));
> > + GSList *class_list = NULL;
> >
> > do {
> > - qdev_prop_set_globals_for_type(dev, object_class_get_name(class));
> > + class_list = g_slist_prepend(class_list, class);
> > class = object_class_get_parent(class);
> > } while (class);
> > +
> > + do {
> > + GSList *head = class_list;
> > +
> > + qdev_prop_set_globals_for_type(dev, object_class_get_name(head->data));
> > + class_list = g_slist_next(head);
> > + g_slist_free_1(head);
> > + } while (class_list);
> > }
> >
> > /* --- 64bit unsigned int 'size' type --- */
> >
>
> It is a bit unfortunate that we need a double loop here, but I don't
> see any good alternative.
>
next prev parent reply other threads:[~2016-12-05 19:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 15:21 [Qemu-devel] [PATCH for-2.8] qdev: apply global properties in reverse order Greg Kurz
2016-12-05 15:42 ` Cornelia Huck
2016-12-05 16:01 ` Cornelia Huck
2016-12-06 8:27 ` Greg Kurz
2016-12-05 16:48 ` Eduardo Habkost
2016-12-05 17:25 ` Cornelia Huck
2016-12-05 17:41 ` Eduardo Habkost
2016-12-05 18:14 ` Halil Pasic
2016-12-06 9:11 ` Greg Kurz
2016-12-06 12:38 ` Halil Pasic
2016-12-06 9:30 ` Greg Kurz
2016-12-06 12:08 ` Halil Pasic
2016-12-05 19:33 ` Greg Kurz
2016-12-05 19:11 ` Greg Kurz [this message]
2016-12-05 17:34 ` Daniel P. Berrange
2016-12-06 9:47 ` Stefan Hajnoczi
2016-12-06 9:54 ` Greg Kurz
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=20161205201156.46b0116b@bahia \
--to=groug@kaod.org \
--cc=cornelia.huck@de.ibm.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=stefanha@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).