|
From: | Markus Armbruster |
Subject: | Re: [Qemu-devel] [PATCH v3 0/2] spapr: QMP: add query-hotpluggable-cpus |
Date: | Tue, 22 Mar 2016 15:22:59 +0100 |
User-agent: | Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) |
Igor Mammedov <address@hidden> writes: > Changes since v2: > - rebase on top of hte lates spapr cpu hotpug series > - add 'vcpus-count' field, address@hidden > - 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/address@hidden/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.
[Prev in Thread] | Current Thread | [Next in Thread] |