All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@pond.sub.org>
To: "Michal Prívozník" <mprivozn@redhat.com>
Cc: qemu-devel@nongnu.org, devel@lists.libvirt.org,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>
Subject: Re: Why device-list-properties?
Date: Thu, 19 Nov 2026 15:41:11 +0100	[thread overview]
Message-ID: <87zev4anp4.fsf@pond.sub.org> (raw)
In-Reply-To: <66383708-4218-48d2-a634-3c4c3e21174e@redhat.com> ("Michal Prívozník"'s message of "Thu, 19 Nov 2026 11:38:30 +0100")

Michal Prívozník <mprivozn@redhat.com> writes:

> On 11/19/26 10:17, 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 think it's only by inertia (from libvirt's POV). I mean,
> device-list-properties was introduced to libvirt in 2012
> (v1.0.0-rc1~216) and qom-list-properties in 2018 (v4.4.0-rc1~209). Are
> you looking at obsoleting the former? If so, libvirt should adapt.

I indeed wonder whether we could deprecate device-list-properties in
favor of qom-list-properties.


  reply	other threads:[~2026-11-19 14:41 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 [this message]
2026-11-19 11:47 ` Daniel P. Berrangé

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=87zev4anp4.fsf@pond.sub.org \
    --to=armbru@pond.sub.org \
    --cc=berrange@redhat.com \
    --cc=devel@lists.libvirt.org \
    --cc=mprivozn@redhat.com \
    --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.