From: Suraj Jitindar Singh <sjitindarsingh@gmail.com>
To: David Gibson <david@gibson.dropbear.id.au>,
groug@kaod.org, clg@kaod.org, aik@ozlabs.ru,
mdroth@linux.vnet.ibm.com, nikunj@linux.vnet.ibm.com
Cc: quintela@redhat.com, sursingh@redhat.com, qemu-devel@nongnu.org,
armbru@redhat.com, qemu-ppc@nongnu.org, abologna@redhat.com,
sbobroff@redhat.com, dgilbert@redhat.com
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCHv4 5/5] ppc: Rework CPU compatibility testing across migration
Date: Thu, 01 Jun 2017 16:23:10 +1000 [thread overview]
Message-ID: <1496298190.4414.2.camel@gmail.com> (raw)
In-Reply-To: <20170526052319.28096-6-david@gibson.dropbear.id.au>
On Fri, 2017-05-26 at 15:23 +1000, David Gibson wrote:
> Migrating between different CPU versions is a bit complicated for
> ppc.
> A long time ago, we ensured identical CPU versions at either end by
> checking the PVR had the same value. However, this breaks under KVM
> HV, because we always have to use the host's PVR - it's not
> virtualized. That would mean we couldn't migrate between hosts with
> different PVRs, even if the CPUs are close enough to compatible in
> practice (sometimes identical cores with different surrounding logic
> have different PVRs, so this happens in practice quite often).
>
> So, we removed the PVR check, but instead checked that several flags
> indicating supported instructions matched. This turns out to be a
> bad
> idea, because those instruction masks are not architected
> information, but
> essentially a TCG implementation detail. So changes to qemu internal
> CPU
> modelling can break migration - this happened between qemu-2.6 and
> qemu-2.7. That was addressed by 146c11f1 "target-ppc: Allow eventual
> removal of old migration mistakes".
>
> Now, verification of CPU compatibility across a migration basically
> doesn't
> happen. We simply ignore the PVR of the incoming migration, and hope
> the
> cpu on the destination is close enough to work.
>
> Now that we've cleaned up handling of processor compatibility modes
> for
> pseries machine type, we can do better. We allow migration if:
>
> * The source and destination PVRs are for the same type of CPU,
> as
> determined by CPU class's pvr_match function
> OR * When the source was in a compatibility mode, and the
> destination CPU
> supports the same compatibility mode
>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Looks good to me.
Reviewed-by: Suraj Jitindar Singh <sjitindarsingh@gmail.com>
> ---
> target/ppc/machine.c | 72
> +++++++++++++++++++++++++++++++++++++++++++++++++---
> 1 file changed, 69 insertions(+), 3 deletions(-)
>
> diff --git a/target/ppc/machine.c b/target/ppc/machine.c
> index 6cb3a48..2c6d9dc 100644
> --- a/target/ppc/machine.c
> +++ b/target/ppc/machine.c
> @@ -8,6 +8,7 @@
> #include "helper_regs.h"
> #include "mmu-hash64.h"
> #include "migration/cpu.h"
> +#include "qapi/error.h"
>
> static int cpu_load_old(QEMUFile *f, void *opaque, int version_id)
> {
> @@ -195,6 +196,30 @@ static void cpu_pre_save(void *opaque)
> }
> }
>
> +/*
> + * Determine if a given PVR is a "close enough" match to the CPU
> + * object. For TCG and KVM PR it would probably be sufficient to
> + * require an exact PVR match. However for KVM HV the user is
> + * restricted to a PVR exactly matching the host CPU. The correct
> way
> + * to handle this is to put the guest into an architected
> + * compatibility mode. However, to allow a more forgiving
> transition
> + * and migration from before this was widely done, we allow
> migration
> + * between sufficiently similar PVRs, as determined by the CPU
> class's
> + * pvr_match() hook.
> + */
> +static bool pvr_match(PowerPCCPU *cpu, uint32_t pvr)
> +{
> + PowerPCCPUClass *pcc = POWERPC_CPU_GET_CLASS(cpu);
> +
> + if (pvr == pcc->pvr) {
> + return true;
> + }
> + if (pcc->pvr_match) {
> + return pcc->pvr_match(pcc, pvr);
> + }
> + return false;
> +}
> +
> static int cpu_post_load(void *opaque, int version_id)
> {
> PowerPCCPU *cpu = opaque;
> @@ -203,10 +228,31 @@ static int cpu_post_load(void *opaque, int
> version_id)
> target_ulong msr;
>
> /*
> - * We always ignore the source PVR. The user or management
> - * software has to take care of running QEMU in a compatible
> mode.
> + * If we're operating in compat mode, we should be ok as long as
> + * the destination supports the same compatiblity mode.
> + *
> + * Otherwise, however, we require that the destination has
> exactly
> + * the same CPU model as the source.
> */
> - env->spr[SPR_PVR] = env->spr_cb[SPR_PVR].default_value;
> +
> +#if defined(TARGET_PPC64)
> + if (cpu->compat_pvr) {
> + Error *local_err = NULL;
> +
> + ppc_set_compat(cpu, cpu->compat_pvr, &local_err);
> + if (local_err) {
> + error_report_err(local_err);
> + error_free(local_err);
> + return -1;
> + }
> + } else
> +#endif
> + {
> + if (!pvr_match(cpu, env->spr[SPR_PVR])) {
> + return -1;
> + }
> + }
> +
> env->lr = env->spr[SPR_LR];
> env->ctr = env->spr[SPR_CTR];
> cpu_write_xer(env, env->spr[SPR_XER]);
> @@ -560,6 +606,25 @@ static const VMStateDescription vmstate_tlbmas =
> {
> }
> };
>
> +static bool compat_needed(void *opaque)
> +{
> + PowerPCCPU *cpu = opaque;
> +
> + assert(!(cpu->compat_pvr && !cpu->vhyp));
> + return (cpu->compat_pvr != 0);
> +}
> +
> +static const VMStateDescription vmstate_compat = {
> + .name = "cpu/compat",
> + .version_id = 1,
> + .minimum_version_id = 1,
> + .needed = compat_needed,
> + .fields = (VMStateField[]) {
> + VMSTATE_UINT32(compat_pvr, PowerPCCPU),
> + VMSTATE_END_OF_LIST()
> + }
> +};
> +
> const VMStateDescription vmstate_ppc_cpu = {
> .name = "cpu",
> .version_id = 5,
> @@ -613,6 +678,7 @@ const VMStateDescription vmstate_ppc_cpu = {
> &vmstate_tlb6xx,
> &vmstate_tlbemb,
> &vmstate_tlbmas,
> + &vmstate_compat,
> NULL
> }
> };
next prev parent reply other threads:[~2017-06-01 6:23 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 5:23 [Qemu-devel] [PATCHv4 0/5] Clean up compatibility mode handling David Gibson
2017-05-26 5:23 ` [Qemu-devel] [PATCHv4 1/5] qapi: add explicit null to string input and output visitors David Gibson
2017-05-26 5:23 ` [Qemu-devel] [PATCHv4 2/5] migration: Mark CPU states dirty before incoming migration/loadvm David Gibson
2017-05-29 20:46 ` Greg Kurz
2017-05-30 6:15 ` David Gibson
2017-05-30 9:14 ` Dr. David Alan Gilbert
2017-05-30 13:03 ` Juan Quintela
2017-05-26 5:23 ` [Qemu-devel] [PATCHv4 3/5] pseries: Move CPU compatibility property to machine David Gibson
2017-06-01 5:44 ` [Qemu-devel] [Qemu-ppc] " Suraj Jitindar Singh
2017-06-01 7:13 ` David Gibson
2017-06-01 7:29 ` Greg Kurz
2017-06-01 12:24 ` David Gibson
2017-06-01 15:44 ` Greg Kurz
2017-05-26 5:23 ` [Qemu-devel] [PATCHv4 4/5] pseries: Reset CPU compatibility mode David Gibson
2017-05-26 5:23 ` [Qemu-devel] [PATCHv4 5/5] ppc: Rework CPU compatibility testing across migration David Gibson
2017-06-01 6:23 ` Suraj Jitindar Singh [this message]
2017-06-01 8:23 ` Greg Kurz
2017-06-02 2:25 ` David Gibson
2017-05-29 23:14 ` [Qemu-devel] [PATCHv4 0/5] Clean up compatibility mode handling Greg Kurz
2017-05-30 6:18 ` David Gibson
2017-05-30 8:01 ` Greg Kurz
2017-05-31 2:57 ` David Gibson
2017-05-31 8:58 ` Greg Kurz
2017-06-01 6:52 ` David Gibson
2017-06-01 11:59 ` Cédric Le Goater
2017-06-01 13:09 ` Greg Kurz
2017-06-02 2:00 ` David Gibson
2017-06-02 8:15 ` Greg Kurz
2017-06-04 11:09 ` David Gibson
2017-06-02 1:55 ` David Gibson
2017-06-01 6:59 ` no-reply
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=1496298190.4414.2.camel@gmail.com \
--to=sjitindarsingh@gmail.com \
--cc=abologna@redhat.com \
--cc=aik@ozlabs.ru \
--cc=armbru@redhat.com \
--cc=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=dgilbert@redhat.com \
--cc=groug@kaod.org \
--cc=mdroth@linux.vnet.ibm.com \
--cc=nikunj@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=quintela@redhat.com \
--cc=sbobroff@redhat.com \
--cc=sursingh@redhat.com \
/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).