From: Markus Armbruster <armbru@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: "Marc-André Lureau" <marcandre.lureau@gmail.com>,
qemu-devel@nongnu.org, pbonzini@redhat.com, berrange@redhat.com,
eduardo@habkost.net, philmd@linaro.org
Subject: Re: [PATCH 3/3] qdev: Legacy properties are now unused, drop
Date: Wed, 03 Dec 2025 10:56:56 +0100 [thread overview]
Message-ID: <87h5u7q45z.fsf@pond.sub.org> (raw)
In-Reply-To: <87ms5jf83d.fsf@pond.sub.org> (Markus Armbruster's message of "Wed, 22 Oct 2025 14:12:54 +0200")
Markus Armbruster <armbru@redhat.com> writes:
> Marc-André Lureau <marcandre.lureau@gmail.com> writes:
>
>> Hi
>>
>>
>> On Wed, Oct 22, 2025 at 2:15 PM Markus Armbruster <armbru@redhat.com> wrote:
>>>
>>> Signed-off-by: Markus Armbruster <armbru@redhat.com>
>>
>> I don't think we have much reasonable way to use those "legacy-*"
>> properties from qom-get and similar, so it's probably ok to just
>> remove them without deprecation.
>
> Almost all of them are unreadable via qom-get:
>
> (qemu) qom-get /machine/unattached/device[3]/pm bus
> "/machine/i440fx/pci.0"
> (qemu) qom-get /machine/unattached/device[3]/pm legacy-bus
> Error: Property 'PIIX4_PM.legacy-bus' is not readable
>
> Same for all the other properties where the qdev property doesn't have a
> .get().
>
> Only the ones with a .print() are readable, i.e. only PCI address
> properties:
>
> (qemu) qom-get /machine/unattached/device[3]/pm addr
> 11
> (qemu) qom-get /machine/unattached/device[3]/pm legacy-addr
> "01.3"
>
> PATCH 2's commit message explains why.
>
> If a deprecation period is wanted, I'll replace this patch.
>
> If not, I can work the above into the commit message.
In my tree now:
qdev: Legacy properties are now unused internally, drop
Legacy properties are an accidental and undocumented external
interface. qom-set doesn't work for them (no .set() method). qom-get
and qom-list-get work only when the underlying qdev property has a
.print() method, i.e. the PCI address properties, as explained in the
previous commit. Here's one that works:
(qemu) qom-get /machine/unattached/device[3]/pm addr
11
(qemu) qom-get /machine/unattached/device[3]/pm legacy-addr
"01.3"
And here's one that doesn't:
(qemu) qom-get /machine/unattached/device[3]/pm bus
"/machine/i440fx/pci.0"
(qemu) qom-get /machine/unattached/device[3]/pm legacy-bus
Error: Property 'PIIX4_PM.legacy-bus' is not readable
Actual use of this undocumented interface seems quite unlikely. A
deprecation period seems unnecessary. Drop it.
>> Acked-by: Marc-André Lureau <marcandre.lureau@redhat.com>
>
> Thanks!
next prev parent reply other threads:[~2025-12-03 9:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 10:14 [PATCH 0/3] qdev: Fix "info qtree" to show links Markus Armbruster
2025-10-22 10:14 ` [PATCH 1/3] qdev: Change PropertyInfo method print() to return malloc'ed string Markus Armbruster
2025-10-22 10:59 ` Marc-André Lureau
2025-10-22 14:08 ` Markus Armbruster
2025-10-22 10:14 ` [PATCH 2/3] qdev: Fix "info qtree" to show links Markus Armbruster
2025-10-22 11:00 ` Marc-André Lureau
2025-10-24 7:05 ` Paolo Bonzini
2025-10-28 10:33 ` Markus Armbruster
2025-10-28 10:59 ` Daniel P. Berrangé
2025-10-28 13:10 ` Paolo Bonzini
2025-10-28 11:04 ` Peter Maydell
2025-10-28 12:58 ` Paolo Bonzini
2025-11-07 13:02 ` Markus Armbruster
2025-11-22 9:10 ` Markus Armbruster
2025-10-22 10:14 ` [PATCH 3/3] qdev: Legacy properties are now unused, drop Markus Armbruster
2025-10-22 11:13 ` Marc-André Lureau
2025-10-22 12:12 ` Markus Armbruster
2025-12-03 9:56 ` Markus Armbruster [this message]
2025-12-03 9:58 ` [PATCH 0/3] qdev: Fix "info qtree" to show links Markus Armbruster
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=87h5u7q45z.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eduardo@habkost.net \
--cc=marcandre.lureau@gmail.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--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.