From: Igor Mammedov <imammedo@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: qemu-devel@nongnu.org, "Markus Armbruster" <armbru@redhat.com>,
"Andreas Färber" <afaerber@suse.de>,
"Daniel P. Berrange" <berrange@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 5/8] qdev: Register static properties as class properties
Date: Thu, 27 Oct 2016 17:30:30 +0200 [thread overview]
Message-ID: <20161027173030.3d0e341d@nial.brq.redhat.com> (raw)
In-Reply-To: <20161027145742.GL5057@thinpad.lan.raisama.net>
On Thu, 27 Oct 2016 12:57:42 -0200
Eduardo Habkost <ehabkost@redhat.com> wrote:
> On Thu, Oct 27, 2016 at 04:51:39PM +0200, Igor Mammedov wrote:
> > On Wed, 26 Oct 2016 14:30:23 -0200
> > Eduardo Habkost <ehabkost@redhat.com> wrote:
> >
> > > Instead of registering qdev static properties on instance_init,
> > > register them as class properties, at qdev_class_set_props().
> > >
> > > qdev_property_add_legacy() was replaced by an equivalent
> > > qdev_class_property_add_legacy() function.
> > > qdev_property_add_static(), on the other hand, can't be
> > > eliminated yet because it is used by arm_cpu_post_init().
> > >
> > > Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
> > > ---
> > > Changes series v1 -> v2:
> > > * (none)
> > >
> > > Changes v2 -> v3:
> > > * Fix code alignemnt
> > > * Reported-by: Igor Mammedov <imammedo@redhat.com>
> > > ---
> > > hw/core/qdev.c | 71 ++++++++++++++++++++++++++++++++++++++++++++++++----------
> > > 1 file changed, 59 insertions(+), 12 deletions(-)
> > >
> > > diff --git a/hw/core/qdev.c b/hw/core/qdev.c
> > > index 85952e8..a88753c 100644
> > > --- a/hw/core/qdev.c
> > > +++ b/hw/core/qdev.c
> > > @@ -739,12 +739,12 @@ static void qdev_get_legacy_property(Object *obj, Visitor *v,
> > > }
> > >
> > > /**
> > > - * qdev_property_add_legacy:
> > > - * @dev: Device to add the property to.
> > > + * qdev_class_property_add_legacy:
> > > + * @oc: Device to add the property to.
> > s/Device/Class/
>
> Thanks, I will fix it.
>
> >
> >
> > > * @prop: The qdev property definition.
> > > * @errp: location to store error information.
> > > *
> > > - * Add a legacy QOM property to @dev for qdev property @prop.
> > > + * Add a legacy QOM property to @oc for qdev property @prop.
> > > * On error, store error in @errp.
> > > *
> > > * Legacy properties are string versions of QOM properties. The format of
> > [...]
> >
> > "make V=1 check" fails for me with this patch applied:
> >
> > QTEST_QEMU_BINARY=aarch64-softmmu/qemu-system-aarch64 QTEST_QEMU_IMG=qemu-img MALLOC_PERTURB_=${MALLOC_PERTURB_:-$((RANDOM % 255 + 1))} gtester -k --verbose -m=quick tests/device-introspect-test tests/qom-test
> > TEST: tests/device-introspect-test... (pid=275141)
> > /aarch64/device/introspect/list: OK
> > /aarch64/device/introspect/none: OK
> > /aarch64/device/introspect/abstract: OK
> > /aarch64/device/introspect/concrete: Unexpected error in object_property_find() at /home/imammedo/builds/qemu/qom/object.c:1002:
> > Property '.disable_vnet_hdr' not found
>
> Oops! Caused by the e1000e PropertyInfo hack that I tried to
> remove yesterday. See "e1000e: QOM property & configuration
> cleanups".
It's property registration ordering issue exposed by 3/8
simple this this series should include after 3/8:
diff --git a/hw/net/e1000e.c b/hw/net/e1000e.c
index 368d284..b26760d 100644
--- a/hw/net/e1000e.c
+++ b/hw/net/e1000e.c
@@ -671,7 +671,6 @@ static void e1000e_class_init(ObjectClass *class, void *data)
dc->desc = "Intel 82574L GbE Controller";
dc->reset = e1000e_qdev_reset;
dc->vmsd = &e1000e_vmstate;
- device_class_set_props(dc, e1000e_properties);
e1000e_prop_disable_vnet = qdev_prop_uint8;
e1000e_prop_disable_vnet.description = "Do not use virtio headers, "
@@ -683,6 +682,7 @@ static void e1000e_class_init(ObjectClass *class, void *data)
e1000e_prop_subsys = qdev_prop_uint16;
e1000e_prop_subsys.description = "PCI device Subsystem ID";
+ device_class_set_props(dc, e1000e_properties);
set_bit(DEVICE_CATEGORY_NETWORK, dc->categories);
}
or event better fix ordering issues first and then generate 3/8 on top of that.
I wonder how many similar ordering 3/8 causes.
next prev parent reply other threads:[~2016-10-27 15:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 16:30 [Qemu-devel] [PATCH v3 0/8] qdev class properties + abstract class support on device-list-properties Eduardo Habkost
2016-10-26 16:30 ` [Qemu-devel] [PATCH v3 1/8] tests: check-qom-proplist: Remove duplicate "bv" property Eduardo Habkost
2016-10-27 14:13 ` Igor Mammedov
2016-10-26 16:30 ` [Qemu-devel] [PATCH v3 2/8] tests: check-qom-proplist: Use &error_abort to catch errors Eduardo Habkost
2016-10-27 14:16 ` Igor Mammedov
2016-10-26 16:30 ` [Qemu-devel] [PATCH v3 3/8] qdev: device_class_set_props() function Eduardo Habkost
2016-10-26 16:30 ` [Qemu-devel] [PATCH v3 4/8] qdev: Extract property-default code to qdev_property_set_to_default() Eduardo Habkost
2016-10-26 16:30 ` [Qemu-devel] [PATCH v3 5/8] qdev: Register static properties as class properties Eduardo Habkost
2016-10-27 14:51 ` Igor Mammedov
2016-10-27 14:57 ` Eduardo Habkost
2016-10-27 15:30 ` Igor Mammedov [this message]
2016-10-27 16:37 ` Eduardo Habkost
2016-10-29 14:00 ` Igor Mammedov
2016-10-26 16:30 ` [Qemu-devel] [PATCH v3 6/8] qom: object_class_property_iter_init() function Eduardo Habkost
2016-10-27 15:34 ` Igor Mammedov
2016-10-27 16:49 ` Eduardo Habkost
2016-10-26 16:30 ` [Qemu-devel] [PATCH v3 7/8] qmp: Support abstract classes on device-list-properties Eduardo Habkost
2016-10-26 16:30 ` [Qemu-devel] [PATCH v3 8/8] qdev: Warning about using object_class_property_add() in new code Eduardo Habkost
2016-10-26 16:48 ` Peter Maydell
2016-10-26 16:57 ` Eduardo Habkost
2016-10-26 17:57 ` Peter Maydell
2016-10-26 19:36 ` Eduardo Habkost
2016-10-27 19:48 ` [Qemu-devel] [PATCH v3 0/8] qdev class properties + abstract class support on device-list-properties Eduardo Habkost
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=20161027173030.3d0e341d@nial.brq.redhat.com \
--to=imammedo@redhat.com \
--cc=afaerber@suse.de \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=ehabkost@redhat.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 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).