qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Igor Mammedov <imammedo@redhat.com>
To: qemu-devel@nongnu.org
Cc: mjrosato@linux.vnet.ibm.com, pkrempa@redhat.com,
	ehabkost@redhat.com, agraf@suse.de, armbru@redhat.com,
	borntraeger@de.ibm.com, qemu-ppc@nongnu.org,
	bharata@linux.vnet.ibm.com, cornelia.huck@de.ibm.com,
	dgibson@redhat.com, afaerber@suse.de
Subject: [Qemu-devel] [PATCH v3 0/2] spapr: QMP: add query-hotpluggable-cpus
Date: Tue, 15 Mar 2016 14:24:06 +0100	[thread overview]
Message-ID: <1458048248-4605-1-git-send-email-imammedo@redhat.com> (raw)

Changes since v2:
 - rebase on top of hte lates spapr cpu hotpug series
 - add 'vcpus-count' field, pkrempa@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

             reply	other threads:[~2016-03-15 13:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-15 13:24 Igor Mammedov [this message]
2016-03-15 13:24 ` [Qemu-devel] [PATCH v3 1/2] QMP: add query-hotpluggable-cpus Igor Mammedov
2016-03-18 19:26   ` Eduardo Habkost
2016-03-21 10:53     ` Igor Mammedov
2016-03-21 23:39       ` David Gibson
2016-03-22  9:19         ` Igor Mammedov
2016-03-15 13:24 ` [Qemu-devel] [RFC v3 2/2] spapr: implement query-hotpluggable-cpus QMP command Igor Mammedov
2016-03-16  5:19   ` Bharata B Rao
2016-03-16  5:41     ` David Gibson
2016-03-16 15:55     ` Igor Mammedov
2016-03-16 19:29 ` [Qemu-devel] [PATCH v3 0/2] spapr: QMP: add query-hotpluggable-cpus Christian Borntraeger
2016-03-17 13:46   ` Igor Mammedov
2016-03-22 14:22 ` Markus Armbruster
2016-03-22 15:00   ` Igor Mammedov

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=1458048248-4605-1-git-send-email-imammedo@redhat.com \
    --to=imammedo@redhat.com \
    --cc=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=armbru@redhat.com \
    --cc=bharata@linux.vnet.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=dgibson@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=mjrosato@linux.vnet.ibm.com \
    --cc=pkrempa@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    /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).