From: David Gibson <david@gibson.dropbear.id.au>
To: Bharata B Rao <bharata@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org, imammedo@redhat.com,
groug@kaod.org
Subject: Re: [Qemu-devel] [PATCH 1/1] spapr: Ensure CPU cores are added contiguously and removed in LIFO order
Date: Thu, 14 Jul 2016 10:51:27 +1000 [thread overview]
Message-ID: <20160714005127.GH14615@voom.fritz.box> (raw)
In-Reply-To: <1468392620-25599-1-git-send-email-bharata@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 3232 bytes --]
On Wed, Jul 13, 2016 at 12:20:20PM +0530, Bharata B Rao wrote:
> If CPU core addition or removal is allowed in random order leading to
> holes in the core id range (and hence in the cpu_index range), migration
> can fail as migration with holes in cpu_index range isn't yet handled
> correctly.
>
> Prevent this situation by enforcing the addition in contiguous order
> and removal in LIFO order so that we never end up with holes in
> cpu_index range.
>
> Signed-off-by: Bharata B Rao <bharata@linux.vnet.ibm.com>
> ---
> While there is work in progress to support migration when there are holes
> in cpu_index range resulting from out-of-order plug or unplug, this patch
> is intended as a last resort if no easy, risk-free and elegant solution
> emerges before 2.7 dev cycle ends.
Applied to ppc-for-2.7. We can revert it once the problems with
cpu_index are sorted out.
>
> hw/ppc/spapr_cpu_core.c | 21 ++++++++++++++++++++-
> 1 file changed, 20 insertions(+), 1 deletion(-)
>
> diff --git a/hw/ppc/spapr_cpu_core.c b/hw/ppc/spapr_cpu_core.c
> index bc52b3c..4bfc96b 100644
> --- a/hw/ppc/spapr_cpu_core.c
> +++ b/hw/ppc/spapr_cpu_core.c
> @@ -126,12 +126,23 @@ static void spapr_core_release(DeviceState *dev, void *opaque)
> void spapr_core_unplug(HotplugHandler *hotplug_dev, DeviceState *dev,
> Error **errp)
> {
> + sPAPRMachineState *spapr = SPAPR_MACHINE(OBJECT(hotplug_dev));
> CPUCore *cc = CPU_CORE(dev);
> sPAPRDRConnector *drc =
> spapr_dr_connector_by_id(SPAPR_DR_CONNECTOR_TYPE_CPU, cc->core_id);
> sPAPRDRConnectorClass *drck;
> Error *local_err = NULL;
> + int smt = kvmppc_smt_threads();
> + int index = cc->core_id / smt;
> + int spapr_max_cores = max_cpus / smp_threads;
> + int i;
>
> + for (i = spapr_max_cores - 1; i > index; i--) {
> + if (spapr->cores[i]) {
> + error_setg(errp, "core-id %d should be removed first", i * smt);
> + return;
> + }
> + }
> g_assert(drc);
>
> drck = SPAPR_DR_CONNECTOR_GET_CLASS(drc);
> @@ -214,7 +225,7 @@ void spapr_core_pre_plug(HotplugHandler *hotplug_dev, DeviceState *dev,
> sPAPRMachineClass *smc = SPAPR_MACHINE_GET_CLASS(OBJECT(hotplug_dev));
> sPAPRMachineState *spapr = SPAPR_MACHINE(OBJECT(hotplug_dev));
> int spapr_max_cores = max_cpus / smp_threads;
> - int index;
> + int index, i;
> int smt = kvmppc_smt_threads();
> Error *local_err = NULL;
> CPUCore *cc = CPU_CORE(dev);
> @@ -252,6 +263,14 @@ void spapr_core_pre_plug(HotplugHandler *hotplug_dev, DeviceState *dev,
> goto out;
> }
>
> + for (i = 0; i < index; i++) {
> + if (!spapr->cores[i]) {
> + error_setg(&local_err, "core-id %d should be added first",
> + i * smt);
> + goto out;
> + }
> + }
> +
> out:
> g_free(base_core_type);
> error_propagate(errp, local_err);
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-07-14 1:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 6:50 [Qemu-devel] [PATCH 1/1] spapr: Ensure CPU cores are added contiguously and removed in LIFO order Bharata B Rao
2016-07-13 7:42 ` Igor Mammedov
2016-07-13 8:19 ` Igor Mammedov
2016-07-13 8:23 ` Igor Mammedov
2016-07-13 9:20 ` [Qemu-devel] [Qemu-ppc] " Greg Kurz
2016-07-14 0:51 ` David Gibson [this message]
2016-07-14 8:27 ` [Qemu-devel] " Igor Mammedov
2016-07-15 5:29 ` David Gibson
2016-07-15 5:35 ` Bharata B Rao
2016-07-15 9:15 ` 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=20160714005127.GH14615@voom.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=bharata@linux.vnet.ibm.com \
--cc=groug@kaod.org \
--cc=imammedo@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).