From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, devel@lists.libvirt.org,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: Why device-list-properties?
Date: Thu, 19 Nov 2026 11:47:43 +0000 [thread overview]
Message-ID: <av7h37W8MuVFlxVK@redhat.com> (raw)
In-Reply-To: <87a4n5ch94.fsf@pond.sub.org>
On Thu, Nov 19, 2026 at 10:17:27AM +0100, Markus Armbruster wrote:
> As far as I can tell, device-list-properties can do nothing you can't do
> with qom-list-properties.
>
> Both take a QOM type name.
>
> device-list-properties rejects types that aren't concrete subtypes of
> "device".
>
> device-list-properties filters out properties named "type", "realized",
> "hotpluggable", "hotplugged", and "parent_bus". These are precisely the
> properties every device inherits from "device".
>
> Why is that useful?
I guess someone considered those to be internal propperties not
relevant to report to client apps.
With UserCreatable Objects, we have QAPI schema to define what are
public properties. One day we should extend that to other objects.
so public vs internal is clear.
None the less, I'm not seeing an obvious reason for device-list-properties
to be kept, if we intend qom-list-properties to stick around.
With regards,
Daniel
--
|: https://berrange.com ~~ https://hachyderm.io/@berrange :|
|: https://libvirt.org ~~ https://entangle-photo.org :|
|: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
prev parent reply other threads:[~2026-11-19 11:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 9:17 Why device-list-properties? Markus Armbruster
2026-11-19 10:38 ` Michal Prívozník
2026-11-19 14:41 ` Markus Armbruster
2026-11-19 11:47 ` Daniel P. Berrangé [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=av7h37W8MuVFlxVK@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=devel@lists.libvirt.org \
--cc=pbonzini@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.