From: Eric Blake <eblake@redhat.com>
To: liguang <lig.fnst@cn.fujitsu.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>, "Alexander Graf" <agraf@suse.de>,
"Anthony Liguori" <aliguori@us.ibm.com>,
"Juan Quintela" <quintela@redhat.com>,
"Stefan Berger" <stefanb@linux.vnet.ibm.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org,
"Christian Borntraeger" <borntraeger@de.ibm.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Joel Schopp" <jschopp@linux.vnet.ibm.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Igor Mammedov" <imammedo@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Luiz Capitulino" <lcapitulino@redhat.com>,
"Andreas Färber" <afaerber@suse.de>,
"Isaku Yamahata" <yamahata@valinux.co.jp>
Subject: Re: [Qemu-devel] [PATCH RFC 6/7] qmp: add 'cpu-del' command
Date: Tue, 28 May 2013 20:33:26 -0600 [thread overview]
Message-ID: <51A568F6.4080808@redhat.com> (raw)
In-Reply-To: <1369792062-14269-7-git-send-email-lig.fnst@cn.fujitsu.com>
[-- Attachment #1: Type: text/plain, Size: 901 bytes --]
On 05/28/2013 07:47 PM, liguang wrote:
> add 'cpu-del' as complementary of 'cpu-add',
> cpu-del doesn't really delete a previous created
> cpu for it depends on CPU-QOM which it's un-finished
> yet to unrealize it.
> cpu-del just records the cpu-id that guest want to
> remove to keep status of ACPI cpu hot-remove process.
>
> Signed-off-by: liguang <lig.fnst@cn.fujitsu.com>
> ---
> +++ b/qapi-schema.json
> @@ -1403,6 +1403,19 @@
> { 'command': 'cpu-add', 'data': {'id': 'int'} }
>
> ##
> +# @cpu-del
> +#
> +# Deletes CPU with specified ID
> +#
> +# @id: ID of CPU to be created, valid values [0..max_cpus)
s/created/unplugged/
> +#
> +# Returns: Nothing on success
> +#
> +# Since 1.6
> +##
> +{ 'command': 'cpu-del', 'data': {'id': 'int'} }
> +
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]
next prev parent reply other threads:[~2013-05-29 2:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 1:47 [Qemu-devel] [PATCH RFC 0/7] pass cpu online/offline event bewteen QEMU and linux kernel by ACPI Embedded Controller liguang
2013-05-29 1:47 ` [Qemu-devel] [PATCH RFC 1/7] acpi: add ACPI Embedded Controller support liguang
2013-05-29 1:47 ` [Qemu-devel] [PATCH RFC 2/7] ich9: add notifer for ec to generate sci liguang
2013-05-29 1:47 ` [Qemu-devel] [PATCH RFC 3/7] ec: add operations for _Qxx events liguang
2013-05-29 1:47 ` [Qemu-devel] [PATCH RFC 4/7] piix4: add notifer for ec to generate sci liguang
2013-05-29 1:47 ` [Qemu-devel] [PATCH RFC 5/7] piix4: add events for cpu hotplug liguang
2013-05-29 1:47 ` [Qemu-devel] [PATCH RFC 6/7] qmp: add 'cpu-del' command liguang
2013-05-29 2:33 ` Eric Blake [this message]
2013-05-29 2:43 ` li guang
2013-05-29 1:47 ` [Qemu-devel] [PATCH RFC 7/7] pc: add EC qdev init for piix & q35 liguang
2013-05-30 14:14 ` [Qemu-devel] [PATCH RFC 0/7] pass cpu online/offline event bewteen QEMU and linux kernel by ACPI Embedded Controller Igor Mammedov
2013-05-31 0:13 ` li guang
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=51A568F6.4080808@redhat.com \
--to=eblake@redhat.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.com \
--cc=armbru@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=imammedo@redhat.com \
--cc=jschopp@linux.vnet.ibm.com \
--cc=kraxel@redhat.com \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=lig.fnst@cn.fujitsu.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanb@linux.vnet.ibm.com \
--cc=yamahata@valinux.co.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.