From: David Gibson <dgibson@redhat.com>
To: Bharata B Rao <bharata@linux.vnet.ibm.com>
Cc: mjrosato@linux.vnet.ibm.com, agraf@suse.de, pkrempa@redhat.com,
ehabkost@redhat.com, qemu-devel@nongnu.org, armbru@redhat.com,
borntraeger@de.ibm.com, qemu-ppc@nongnu.org,
cornelia.huck@de.ibm.com, Igor Mammedov <imammedo@redhat.com>,
afaerber@suse.de
Subject: Re: [Qemu-devel] [RFC v3 2/2] spapr: implement query-hotpluggable-cpus QMP command
Date: Wed, 16 Mar 2016 16:41:36 +1100 [thread overview]
Message-ID: <20160316164136.74299a4d@voom.fritz.box> (raw)
In-Reply-To: <20160316051941.GE13176@in.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 2680 bytes --]
On Wed, 16 Mar 2016 10:49:41 +0530
Bharata B Rao <bharata@linux.vnet.ibm.com> wrote:
> On Tue, Mar 15, 2016 at 02:24:08PM +0100, Igor Mammedov wrote:
> > it returns a list of present/possible to hotplug CPU
> > objects with a list of properties to use with
> > device_add.
> >
> > in spapr case returned list would looks like:
> > -> { "execute": "query-hotpluggable-cpus" }
> > <- {"return": [
> > { "props": { "core": 1 }, "type": "spapr-cpu-core",
> > "vcpus-count": 2 },
> > { "props": { "core": 0 }, "type": "spapr-cpu-core",
> > "vcpus-count": 2,
> > "qom-path": "/machine/unattached/device[0]"}
> > ]}'
> >
> > TODO:
> > add 'node' property for core <-> numa node mapping
> >
> > Signed-off-by: Igor Mammedov <imammedo@redhat.com>
> > ---
> > it's only compile tested
> > ---
> > hw/ppc/spapr.c | 32 ++++++++++++++++++++++++++++++++
> > 1 file changed, 32 insertions(+)
> >
> > diff --git a/hw/ppc/spapr.c b/hw/ppc/spapr.c
> > index b1e9ba2..e1ce983 100644
> > --- a/hw/ppc/spapr.c
> > +++ b/hw/ppc/spapr.c
> > @@ -65,6 +65,7 @@
> > #include "hw/compat.h"
> > #include "qemu-common.h"
> > #include "hw/ppc/spapr_cpu_core.h"
> > +#include "qmp-commands.h"
> >
> > #include <libfdt.h>
> >
> > @@ -2399,6 +2400,37 @@ static unsigned spapr_cpu_index_to_socket_id(unsigned cpu_index)
> > return cpu_index / smp_threads / smp_cores;
> > }
> >
> > +HotpluggableCPUList *qmp_query_hotpluggable_cpus(Error **errp)
> > +{
> > + int i;
> > + HotpluggableCPUList *head = NULL;
> > + sPAPRMachineState *spapr = SPAPR_MACHINE(qdev_get_machine());
> > + int spapr_max_cores = max_cpus / smp_threads;
> > +
> > + for (i = 0; i < spapr_max_cores; i++) {
> > + HotpluggableCPUList *list_item = g_new0(typeof(*list_item), 1);
> > + HotpluggableCPU *cpu_item = g_new0(typeof(*cpu_item), 1);
> > + CpuInstanceProperties *cpu_props = g_new0(typeof(*cpu_props), 1);
> > +
> > + cpu_item->type = g_strdup(TYPE_SPAPR_CPU_CORE);
> > + cpu_item->vcpus_count = smp_threads;
>
> Shouldn't this be fetched from "threads" property of the core device
> instead of directly using smp_threads ? But again, what that would mean
> for not-yet-plugged in cores and how to get that for them is a question.
Yeah, I think Igor's patch is correct here. The information flow goes
the other direction: the machine type code advertises smp_threads here,
which management then passes back to the device_add spapr-core in the
threads property.
--
David Gibson <dgibson@redhat.com>
Senior Software Engineer, Virtualization, Red Hat
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-03-16 5:40 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 [this message]
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=20160316164136.74299a4d@voom.fritz.box \
--to=dgibson@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=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.