All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: mjrosato@linux.vnet.ibm.com, pkrempa@redhat.com,
	ehabkost@redhat.com, agraf@suse.de, qemu-devel@nongnu.org,
	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: Re: [Qemu-devel] [PATCH v3 0/2] spapr: QMP: add query-hotpluggable-cpus
Date: Tue, 22 Mar 2016 15:22:59 +0100	[thread overview]
Message-ID: <87vb4eoam4.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <1458048248-4605-1-git-send-email-imammedo@redhat.com> (Igor Mammedov's message of "Tue, 15 Mar 2016 14:24:06 +0100")

Igor Mammedov <imammedo@redhat.com> writes:

> 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.

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.

  parent reply	other threads:[~2016-03-22 14:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-15 13:24 [Qemu-devel] [PATCH v3 0/2] spapr: QMP: add query-hotpluggable-cpus Igor Mammedov
2016-03-15 13:24 ` [Qemu-devel] [PATCH v3 1/2] " 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 [this message]
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=87vb4eoam4.fsf@blackfin.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=afaerber@suse.de \
    --cc=agraf@suse.de \
    --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=imammedo@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 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.