From: David Gibson <david@gibson.dropbear.id.au>
To: Greg Kurz <groug@kaod.org>
Cc: Bharata B Rao <bharata@linux.vnet.ibm.com>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org, imammedo@redhat.com,
nikunj@linux.vnet.ibm.com, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [RFC PATCH v2 0/5] sPAPR: Fix migration when CPUs are removed in random order
Date: Fri, 8 Jul 2016 15:34:20 +1000 [thread overview]
Message-ID: <20160708053420.GP14675@voom.fritz.box> (raw)
In-Reply-To: <20160707180410.351fb5eb@bahia.lan>
[-- Attachment #1: Type: text/plain, Size: 1975 bytes --]
On Thu, Jul 07, 2016 at 06:04:10PM +0200, Greg Kurz wrote:
> On Thu, 7 Jul 2016 20:20:20 +0530
> Bharata B Rao <bharata@linux.vnet.ibm.com> wrote:
>
> > device_add/del based CPU hotplug and unplug support is upstream for
> > sPAPR PowerPC and is under development for x86. Both of these will
> > support CPU device removal in random order (and not necessarily in LIFO
> > order). Random order removal will result in holes in cpu_index range
> > which causes migration to fail. This needs fixes in both generic code
> > as well as arch specific code.
> >
> > - CPUState::stable_cpu_id is newly introduced and used as instance_id when
> > registering CPU devices using vmstate_register. stable_cpu_id is set by the
> > target machine code. To support forward migration, as per Igor's
> > suggestion, this needs to be done conditionally based on machine type
> > version.
> > - From pseries-2.7 onwards, we start using stable_cpu_id for migration as
> > well as in XICS code.
> >
> > vmstate registration calls are moved to cpu_common_realizefn and newly
> > introduced cpu_common_unrealizefn.
> >
> > This patchset depends on Greg Kurz's patchset where among other things,
> > he is deriving cpu_dt_it (which is stable_cpu_id for pseries-2.7 onwards)
> > based on core-id and hence is based on ppc-vcpu-dt-id-rework branch of his
> > tree.
> >
>
> I'm not very comfortable with this. Shouldn't it be the other way round
> actually: cpu_dt_id depending on stable_cpu_id ?
>
> I think we're missing something like a stable_core_id.
The core-id is already stable.
Deriving the stable vcpu id from the core id is correct.
cpu_dt_id should actually go away, and we should just use
stable_cpu_id when creating the device tree.
--
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 --]
prev parent reply other threads:[~2016-07-08 5:32 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 14:50 [Qemu-devel] [RFC PATCH v2 0/5] sPAPR: Fix migration when CPUs are removed in random order Bharata B Rao
2016-07-07 14:50 ` [Qemu-devel] [RFC PATCH v2 1/5] cpu, target-ppc: Move cpu_vmstate_[un]register calls to cpu_common_[un]realize Bharata B Rao
2016-07-07 14:50 ` [Qemu-devel] [RFC PATCH v2 2/5] cpu: Introduce CPUState::stable_cpu_id Bharata B Rao
2016-07-07 17:52 ` Greg Kurz
2016-07-08 5:21 ` David Gibson
2016-07-08 5:19 ` David Gibson
2016-07-08 11:11 ` Igor Mammedov
2016-07-11 3:22 ` David Gibson
2016-07-11 3:35 ` Bharata B Rao
2016-07-11 7:42 ` Igor Mammedov
2016-07-11 13:42 ` [Qemu-devel] [PATCH] VARIANT 1: reuse device compat logic to pick preffered CPU's migration instance_id Igor Mammedov
2016-07-11 13:42 ` [Qemu-devel] [PATCH] VARIANT 2: use machine specific callback to pick " Igor Mammedov
2016-07-11 14:15 ` [Qemu-devel] [PATCH] VARIANT 1: reuse device compat logic to pick preffered " Paolo Bonzini
2016-07-12 5:07 ` David Gibson
2016-07-12 8:11 ` Igor Mammedov
2016-07-13 1:39 ` David Gibson
2016-07-12 7:06 ` Bharata B Rao
2016-07-12 8:21 ` Igor Mammedov
2016-07-12 11:08 ` [Qemu-devel] [PATCH v2 1/2] cpu: add migration_id to allow board to provide " Igor Mammedov
2016-07-12 11:08 ` [Qemu-devel] [PATCH v2 2/2] pc: fix migration failure after cpu hot-unplung Igor Mammedov
2016-07-11 7:58 ` [Qemu-devel] [RFC PATCH v2 2/5] cpu: Introduce CPUState::stable_cpu_id Igor Mammedov
2016-07-12 5:09 ` David Gibson
2016-07-07 14:50 ` [Qemu-devel] [RFC PATCH v2 3/5] spapr: Set stable_cpu_id for threads of CPU cores Bharata B Rao
2016-07-07 16:11 ` Greg Kurz
2016-07-08 5:25 ` David Gibson
2016-07-08 7:46 ` Greg Kurz
2016-07-08 7:59 ` David Gibson
2016-07-08 15:24 ` Greg Kurz
2016-07-11 3:23 ` David Gibson
2016-07-08 5:24 ` David Gibson
2016-07-08 6:41 ` Bharata B Rao
2016-07-08 7:39 ` David Gibson
2016-07-08 10:59 ` Igor Mammedov
2016-07-11 3:12 ` Bharata B Rao
2016-07-11 3:26 ` David Gibson
2016-07-11 8:15 ` Igor Mammedov
2016-07-12 4:41 ` David Gibson
2016-07-07 14:50 ` [Qemu-devel] [RFC PATCH v2 4/5] xics: Use stable_cpu_id instead of cpu_index in XICS code Bharata B Rao
2016-07-08 5:32 ` David Gibson
2016-07-07 14:50 ` [Qemu-devel] [RFC PATCH v2 5/5] spapr: Enable the use of stable_cpu_id from pseries-2.7 onwards Bharata B Rao
2016-07-07 16:04 ` [Qemu-devel] [RFC PATCH v2 0/5] sPAPR: Fix migration when CPUs are removed in random order Greg Kurz
2016-07-08 5:34 ` David Gibson [this message]
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=20160708053420.GP14675@voom.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=bharata@linux.vnet.ibm.com \
--cc=groug@kaod.org \
--cc=imammedo@redhat.com \
--cc=nikunj@linux.vnet.ibm.com \
--cc=pbonzini@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).