Re: [Qemu-devel] [PATCH v3 0/2] spapr: QMP: add query-hotpluggable-cpus
On Tue, 22 Mar 2016 15:22:59 +0100 Markus Armbrusterwrote: > Igor Mammedov writes: > > > Changes since v2: > > - rebase on top of hte lates spapr cpu hotpug series > > - add 'vcpus-count' field, pkre...@redhat.com > > - s/CpuInstanceProps/CpuInstanceProperties/ > > - use '#optional' marker > > - make "props" as always present even if it's empty > > - fix JSON examples > > - fix minor typos > > - drop pre_plug spapr impl out of series as not related to QMP command > > - drop generic pre hotplug callback as not related to QMP command > > > > Changes since RFC: > > - drop arch_id > > - move CPU properties into separate structure > > - target implements its own qmp callback version > > - rebased on top of [RFC PATCH v1 00/10] Core based CPU hotplug for > > PowerPC sPAPR > > > > https://www.mail-archive.com/qemu-devel@nongnu.org/msg357567.html > > - convert slot name to core id hack > > - drop links > > - add generic pre hotplug callback > > - implement query-hotpluggable-cpus > > > > The first patch (QMP API) in this series could go in first > > allowing individual targets to post their hotplug > > implementation independently on top of it. > > We discussed the need for a yet another ad hoc query command. Can you > please summarize the discussion and its conclusion? Explaining *why* a > feature is needed is always a good idea. Cover letter and commit > messages are good places for it. Summary would be: that yet another ad hoc query QMP command is 1. a single / atomic command 2. well documented 3. fixed at compile time/staic so it's easy for mgmt to discover it. while a considered alternative QOM interface via qom-get(path) is 1. not atomic, i.e. requires a lot of qom-get commands over the wire to traverse QOM tree and fetch information 2. not documented 3. dynamically generated and would require more complicated coding even to create a simplistic interface similar to proposed QMP command (for example: possible_cpu QOM objects with a related properties) I hope, I haven't missed anything.
Re: [Qemu-devel] [PATCH v3 0/2] spapr: QMP: add query-hotpluggable-cpus
Igor Mammedovwrites: > Changes since v2: > - rebase on top of hte lates spapr cpu hotpug series > - add 'vcpus-count' field, pkre...@redhat.com > - s/CpuInstanceProps/CpuInstanceProperties/ > - use '#optional' marker > - make "props" as always present even if it's empty > - fix JSON examples > - fix minor typos > - drop pre_plug spapr impl out of series as not related to QMP command > - drop generic pre hotplug callback as not related to QMP command > > Changes since RFC: > - drop arch_id > - move CPU properties into separate structure > - target implements its own qmp callback version > - rebased on top of [RFC PATCH v1 00/10] Core based CPU hotplug for PowerPC > sPAPR > > https://www.mail-archive.com/qemu-devel@nongnu.org/msg357567.html > - convert slot name to core id hack > - drop links > - add generic pre hotplug callback > - implement query-hotpluggable-cpus > > The first patch (QMP API) in this series could go in first > allowing individual targets to post their hotplug > implementation independently on top of it. We discussed the need for a yet another ad hoc query command. Can you please summarize the discussion and its conclusion? Explaining *why* a feature is needed is always a good idea. Cover letter and commit messages are good places for it.
Re: [Qemu-devel] [PATCH v3 0/2] spapr: QMP: add query-hotpluggable-cpus
On 03/15/2016 02:24 PM, Igor Mammedov wrote: > Changes since v2: > - rebase on top of hte lates spapr cpu hotpug series > - add 'vcpus-count' field, pkre...@redhat.com > - s/CpuInstanceProps/CpuInstanceProperties/ > - use '#optional' marker > - make "props" as always present even if it's empty > - fix JSON examples > - fix minor typos > - drop pre_plug spapr impl out of series as not related to QMP command > - drop generic pre hotplug callback as not related to QMP command > > Changes since RFC: > - drop arch_id > - move CPU properties into separate structure > - target implements its own qmp callback version > - rebased on top of [RFC PATCH v1 00/10] Core based CPU hotplug for PowerPC > sPAPR > > https://www.mail-archive.com/qemu-devel@nongnu.org/msg357567.html > - convert slot name to core id hack > - drop links > - add generic pre hotplug callback > - implement query-hotpluggable-cpus > > The first patch (QMP API) in this series could go in first > allowing individual targets to post their hotplug > implementation independently on top of it. > > Igor Mammedov (2): > QMP: add query-hotpluggable-cpus > spapr: implement query-hotpluggable-cpus QMP command > > hw/ppc/spapr.c | 32 +++ i might have just missed that, do we also have the x86 implementation already available as RFC somewhere?
Re: [Qemu-devel] [PATCH v3 0/2] spapr: QMP: add query-hotpluggable-cpus
On Wed, 16 Mar 2016 20:29:59 +0100 Christian Borntraegerwrote: > On 03/15/2016 02:24 PM, Igor Mammedov wrote: > > Changes since v2: > > - rebase on top of hte lates spapr cpu hotpug series > > - add 'vcpus-count' field, pkre...@redhat.com > > - s/CpuInstanceProps/CpuInstanceProperties/ > > - use '#optional' marker > > - make "props" as always present even if it's empty > > - fix JSON examples > > - fix minor typos > > - drop pre_plug spapr impl out of series as not related to QMP command > > - drop generic pre hotplug callback as not related to QMP command > > > > Changes since RFC: > > - drop arch_id > > - move CPU properties into separate structure > > - target implements its own qmp callback version > > - rebased on top of [RFC PATCH v1 00/10] Core based CPU hotplug for > > PowerPC sPAPR > > > > https://www.mail-archive.com/qemu-devel@nongnu.org/msg357567.html > > - convert slot name to core id hack > > - drop links > > - add generic pre hotplug callback > > - implement query-hotpluggable-cpus > > > > The first patch (QMP API) in this series could go in first > > allowing individual targets to post their hotplug > > implementation independently on top of it. > > > > Igor Mammedov (2): > > QMP: add query-hotpluggable-cpus > > spapr: implement query-hotpluggable-cpus QMP command > > > > hw/ppc/spapr.c | 32 +++ > > i might have just missed that, do we also have the x86 implementation already > available as > RFC somewhere? device_add x86-cpu, hasn't been posted yet, but I'm working on it. If you are asking about query-hotpluggable-cpus command with x86 backend then it's been posted as v1 of this RFC https://patchwork.ozlabs.org/patch/583036/ and current v3 is what QMP interface evolved to based on feedback for QEMU and libvirt developers. x86 backend shouldn't be hard to respin as prerequisite patches for it were just merged, I plan to stick that patch in device_add enablement series.
[Qemu-devel] [PATCH v3 0/2] spapr: QMP: add query-hotpluggable-cpus
Changes since v2: - rebase on top of hte lates spapr cpu hotpug series - add 'vcpus-count' field, pkre...@redhat.com - s/CpuInstanceProps/CpuInstanceProperties/ - use '#optional' marker - make "props" as always present even if it's empty - fix JSON examples - fix minor typos - drop pre_plug spapr impl out of series as not related to QMP command - drop generic pre hotplug callback as not related to QMP command Changes since RFC: - drop arch_id - move CPU properties into separate structure - target implements its own qmp callback version - rebased on top of [RFC PATCH v1 00/10] Core based CPU hotplug for PowerPC sPAPR https://www.mail-archive.com/qemu-devel@nongnu.org/msg357567.html - convert slot name to core id hack - drop links - add generic pre hotplug callback - implement query-hotpluggable-cpus The first patch (QMP API) in this series could go in first allowing individual targets to post their hotplug implementation independently on top of it. Igor Mammedov (2): QMP: add query-hotpluggable-cpus spapr: implement query-hotpluggable-cpus QMP command hw/ppc/spapr.c | 32 +++ qapi-schema.json| 41 +++ qmp-commands.hx | 43 + stubs/Makefile.objs | 1 + stubs/qmp_query_hotpluggable_cpus.c | 9 5 files changed, 126 insertions(+) create mode 100644 stubs/qmp_query_hotpluggable_cpus.c -- 1.8.3.1