diff options
| author | Markus Armbruster <armbru@redhat.com> | 2024-07-11 13:22:25 +0200 |
|---|---|---|
| committer | Markus Armbruster <armbru@redhat.com> | 2024-07-17 10:15:04 +0200 |
| commit | d07f0efcbca66178d42f8c9c4f624e9de517100a (patch) | |
| tree | 00fb6c80d280b31a77ebe7ba1ff4586ff3c0c3d0 /scripts | |
| parent | fbcb6e0c487abd09cf1fab7913302174c3a2fa16 (diff) | |
| download | qemu-d07f0efcbca66178d42f8c9c4f624e9de517100a.zip qemu-d07f0efcbca66178d42f8c9c4f624e9de517100a.tar.gz qemu-d07f0efcbca66178d42f8c9c4f624e9de517100a.tar.bz2 | |
qapi/machine: Clean up documentation around CpuInstanceProperties
CpuInstanceProperties' doc comment describes its members as properties
to be passed to device_add when hot-plugging a CPU.
This was in fact the initial use of this type, with
query-hotpluggable-cpus: letting management applications find out what
properties need to be passed with device_add to hot-plug a CPU.
We've since added other uses: set-numa-node (commit 419fcdec3c1 and
f3be67812c2), and query-cpus-fast (commit ce74ee3dea6). These are not
about device-add.
query-hotpluggable-cpus uses CpuInstanceProperties within
HotpluggableCPU. Lift the documentation related to device-add from
CpuInstanceProperties to HotpluggableCPU.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-ID: <20240711112228.2140606-3-armbru@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Reviewed-by: John Snow <jsnow@redhat.com>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions