diff options
author | Markus Armbruster <armbru@redhat.com> | 2025-02-27 09:55:57 +0100 |
---|---|---|
committer | Markus Armbruster <armbru@redhat.com> | 2025-03-06 10:09:27 +0100 |
commit | e09daf1dff8f5117b3e482f1907e762470b5675c (patch) | |
tree | 248603b7d6064504addd351eaafd048a6508c2de /rust/qemu-api/src/module.rs | |
parent | 744bce1bf7fecf8b8a8de484328515800f9c9639 (diff) | |
download | qemu-e09daf1dff8f5117b3e482f1907e762470b5675c.zip qemu-e09daf1dff8f5117b3e482f1907e762470b5675c.tar.gz qemu-e09daf1dff8f5117b3e482f1907e762470b5675c.tar.bz2 |
qdev: Change qdev_prop_pci_devfn member @name from "int32" to "str"
Properties using qdev_prop_pci_devfn initially accepted a string of
the form "DEV.FN" or "DEV" where DEV and FN are in hexadecimal.
Member @name was "pci-devfn" initially.
Commit b403298adb5 (qdev: make the non-legacy pci address property
accept an integer) changed them to additionally accept integers: bits
3..7 are DEV, and bits 0..2 are FN. This is inaccessible externally
in device_add so far.
The commit also changed @name to "int32", and set member @legacy-name
to "pci-devfn". Together, this kept QMP command
device-list-properties unaffected: it used @name only when
@legacy_name was null.
Commit 07d09c58dbb (qmp: Print descriptions of object properties)
quietly dumbed that down to use @name always, and the next commit
18b91a3e082q (qdev: Drop legacy_name from qdev properties) dropped
member @legacy_name. This changed the value of @type reported by QMP
command device-list-properties from "pci-devfn" to "int32".
But "int32" is misleading: device_add actually wants QAPI type "str".
So change @name to that.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-ID: <20250227085601.4140852-3-armbru@redhat.com>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Diffstat (limited to 'rust/qemu-api/src/module.rs')
0 files changed, 0 insertions, 0 deletions