qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, "Daniel P. Berrangé" <berrange@redhat.com>,
	"Eduardo Habkost" <eduardo@habkost.net>,
	"Stefan Hajnoczi" <stefanha@redhat.com>
Subject: Re: [PATCH] qdev-properties: alias all object class properties
Date: Thu, 14 Sep 2023 08:44:38 -0400	[thread overview]
Message-ID: <CAJSP0QUO+=01pxry2v71p3c+W2q2uRvUusmDU5ym6L6SFW0n4g@mail.gmail.com> (raw)
In-Reply-To: <20230803195115.2367293-1-stefanha@redhat.com>

Paolo: ping?

On Thu, 3 Aug 2023 at 15:51, Stefan Hajnoczi <stefanha@redhat.com> wrote:
>
> qdev_alias_all_properties() aliases a DeviceState's qdev properties onto
> an Object. This is used for VirtioPCIProxy types so that --device
> virtio-blk-pci has properties of its embedded --device virtio-blk-device
> object.
>
> Currently this function is implemented using qdev properties. Change the
> function to use QOM object class properties instead. This works because
> qdev properties create QOM object class properties, but it also catches
> any QOM object class-only properties that have no qdev properties.
>
> This change ensures that properties of devices are shown with --device
> foo,\? even if they are QOM object class properties.
>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---
>  hw/core/qdev-properties.c | 18 ++++++++++--------
>  1 file changed, 10 insertions(+), 8 deletions(-)
>
> diff --git a/hw/core/qdev-properties.c b/hw/core/qdev-properties.c
> index 357b8761b5..fbf3969d3c 100644
> --- a/hw/core/qdev-properties.c
> +++ b/hw/core/qdev-properties.c
> @@ -959,16 +959,18 @@ void device_class_set_props(DeviceClass *dc, Property *props)
>  void qdev_alias_all_properties(DeviceState *target, Object *source)
>  {
>      ObjectClass *class;
> -    Property *prop;
> +    ObjectPropertyIterator iter;
> +    ObjectProperty *prop;
>
>      class = object_get_class(OBJECT(target));
> -    do {
> -        DeviceClass *dc = DEVICE_CLASS(class);
>
> -        for (prop = dc->props_; prop && prop->name; prop++) {
> -            object_property_add_alias(source, prop->name,
> -                                      OBJECT(target), prop->name);
> +    object_class_property_iter_init(&iter, class);
> +    while ((prop = object_property_iter_next(&iter))) {
> +        if (object_property_find(source, prop->name)) {
> +            continue; /* skip duplicate properties */
>          }
> -        class = object_class_get_parent(class);
> -    } while (class != object_class_by_name(TYPE_DEVICE));
> +
> +        object_property_add_alias(source, prop->name,
> +                                  OBJECT(target), prop->name);
> +    }
>  }
> --
> 2.41.0
>
>


      reply	other threads:[~2023-09-14 12:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-03 19:51 [PATCH] qdev-properties: alias all object class properties Stefan Hajnoczi
2023-09-14 12:44 ` Stefan Hajnoczi [this message]

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='CAJSP0QUO+=01pxry2v71p3c+W2q2uRvUusmDU5ym6L6SFW0n4g@mail.gmail.com' \
    --to=stefanha@gmail.com \
    --cc=berrange@redhat.com \
    --cc=eduardo@habkost.net \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@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).