From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, pbonzini@redhat.com
Subject: Re: [PATCH] qom: Fix device-list-properties & friends to show legacy-FOO props
Date: Wed, 8 Jul 2026 16:08:52 +0100 [thread overview]
Message-ID: <ak5oBDQkpBCYwlkB@redhat.com> (raw)
In-Reply-To: <20260708140948.2622814-1-armbru@redhat.com>
On Wed, Jul 08, 2026 at 04:09:48PM +0200, Markus Armbruster wrote:
> qmp_device_list_properties() skips properties whose name starts with
> "legacy-". This is a flawed test for "is a legacy property".
>
> The test is flawed because non-legacy properties can and do start with
> "legacy-". Back when it was added, no such properties existed. Right
> now, three such properties do: property "legacy-cmb" of device "nvme",
> and properties "legacy-cache" and "legacy-multi-node" of devices
> "x86_64-cpu", "i386-cpu", and its children.
>
> This affects QMP command "device-list-properties", HMP command
> "device_add T,help", and command line option "-device T,help".
>
> Legacy properties are gone since commit a61383f7ab (qdev: Legacy
> properties are now unused internally, drop, 2025-10-22). This makes
> the fix easy: delete the code that skips them.
>
> Reproducer: -device nvme,help doesn't show legacy-cmb before the
> patch, and does after.
>
> Fixes: f4eb32b590 (qmp: show QOM properties in device-list-properties, 2014-05-20)
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> ---
> qom/qom-qmp-cmds.c | 7 -------
> 1 file changed, 7 deletions(-)
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
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-07-08 15:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 14:09 [PATCH] qom: Fix device-list-properties & friends to show legacy-FOO props Markus Armbruster
2026-07-08 15:08 ` 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=ak5oBDQkpBCYwlkB@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@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.