From: Kashyap Chamarthy <kchamart@redhat.com>
To: qemu-devel@nongnu.org
Cc: eblake@redhat.com, armbru@redhat.com, ehabkost@redhat.com,
imammedo@redhat.com, thuth@redhat.com,
Kashyap Chamarthy <kchamart@redhat.com>
Subject: [Qemu-devel] [PATCH v3 1/3] Deprecate QMP `cpu-add`
Date: Tue, 30 Oct 2018 13:35:24 +0100 [thread overview]
Message-ID: <20181030123526.26415-2-kchamart@redhat.com> (raw)
In-Reply-To: <20181030123526.26415-1-kchamart@redhat.com>
The intended functionality of QMP `cpu-add` is replaced with
`device_add` (and `query-hotpluggable-cpus`). So let's deprecate
`cpu-add`.
A complete example of vCPU hotplug with the recommended way (using
`device_add`) is provided as part of a seperate docs patch.
Suggested-by: Eduardo Habkost <ehabkost@redhat.com
Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>
---
---
qapi/misc.json | 8 +++++++-
qemu-deprecated.texi | 5 +++++
2 files changed, 12 insertions(+), 1 deletion(-)
diff --git a/qapi/misc.json b/qapi/misc.json
index d450cfef21..fbee1e6d34 100644
--- a/qapi/misc.json
+++ b/qapi/misc.json
@@ -1104,7 +1104,7 @@
##
# @cpu-add:
#
-# Adds CPU with specified ID
+# Adds CPU with specified ID.
#
# @id: ID of CPU to be created, valid values [0..max_cpus)
#
@@ -1112,6 +1112,10 @@
#
# Since: 1.5
#
+# Note: This command is deprecated. The `device_add` command should be
+# used instead. See the `query-hotpluggable-cpus` command for
+# details.
+#
# Example:
#
# -> { "execute": "cpu-add", "arguments": { "id": 2 } }
@@ -3213,6 +3217,8 @@
##
# @query-hotpluggable-cpus:
#
+# TODO: Better documentation; currently there is none.
+#
# Returns: a list of HotpluggableCPU objects.
#
# Since: 2.7
diff --git a/qemu-deprecated.texi b/qemu-deprecated.texi
index 1b9c007f12..c86924ad9a 100644
--- a/qemu-deprecated.texi
+++ b/qemu-deprecated.texi
@@ -155,6 +155,11 @@ The ``query-cpus'' command is replaced by the ``query-cpus-fast'' command.
The ``arch'' output member of the ``query-cpus-fast'' command is
replaced by the ``target'' output member.
+@subsection cpu-add (since 3.1)
+
+Use ``device_add'' for hotplugging vCPUs instead of ``cpu-add''. See
+documentation of ``query-hotpluggable-cpus'' for additional details.
+
@section System emulator devices
@subsection ivshmem (since 2.6.0)
--
2.17.1
next prev parent reply other threads:[~2018-10-30 12:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 12:35 [Qemu-devel] [PATCH v3 0/3] Deprecate QMP & HMP `cpu-add`; document vCPU hotplug Kashyap Chamarthy
2018-10-30 12:35 ` Kashyap Chamarthy [this message]
2018-11-05 11:11 ` [Qemu-devel] [PATCH v3 1/3] Deprecate QMP `cpu-add` Thomas Huth
2018-12-13 6:38 ` Thomas Huth
2018-12-13 11:05 ` Kashyap Chamarthy
2018-12-13 12:01 ` Kashyap Chamarthy
2018-10-30 12:35 ` [Qemu-devel] [PATCH v3 2/3] Deprecate HMP `cpu-add` Kashyap Chamarthy
2018-10-31 15:14 ` Markus Armbruster
2018-11-05 11:20 ` Thomas Huth
2018-11-07 8:49 ` Kashyap Chamarthy
2018-11-07 9:30 ` Thomas Huth
2018-10-30 12:35 ` [Qemu-devel] [PATCH v3 3/3] docs: Document vCPU hotplug procedure Kashyap Chamarthy
2018-10-30 13:00 ` [Qemu-devel] [PATCH v3 0/3] Deprecate QMP & HMP `cpu-add`; document vCPU hotplug Kashyap Chamarthy
2018-10-30 15:56 ` Michal Privoznik
2018-10-31 15:17 ` Markus Armbruster
2018-10-31 18:24 ` Eduardo Habkost
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=20181030123526.26415-2-kchamart@redhat.com \
--to=kchamart@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).