From: David Gibson <david@gibson.dropbear.id.au>
To: Laurent Vivier <lvivier@redhat.com>
Cc: groug@kaod.org, qemu-ppc@nongnu.org, qemu-devel@nongnu.org, clg@kaod.org
Subject: Re: [Qemu-devel] [PATCH] pseries: Fix compat_pvr on reset
Date: Tue, 27 Aug 2019 13:45:19 +1000 [thread overview]
Message-ID: <20190827034519.GB10107@umbus.fritz.box> (raw)
In-Reply-To: <20190826090812.19080-1-lvivier@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2597 bytes --]
On Mon, Aug 26, 2019 at 11:08:12AM +0200, Laurent Vivier wrote:
> If we a migrate P8 machine to a P9 machine, the migration fails on
> destination with:
>
> error while loading state for instance 0x1 of device 'cpu'
> load of migration failed: Operation not permitted
>
> This is caused because the compat_pvr field is only present for the first
> CPU.
> Originally, spapr_machine_reset() calls ppc_set_compat() to set the value
> max_compat_pvr for the first cpu and this was propagated to all CPUs by
> spapr_cpu_reset(). Now, as spapr_cpu_reset() is called before that, the
> value is not propagated to all CPUs and the migration fails.
>
> To fix that, propagate the new value to all CPUs in spapr_machine_reset().
>
> Fixes: 25c9780d38d4 ("spapr: Reset CAS & IRQ subsystem after devices")
> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
Applied to ppc-for-4.2, thanks.
> ---
> hw/ppc/spapr.c | 8 +++++++-
> hw/ppc/spapr_cpu_core.c | 2 ++
> 2 files changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/hw/ppc/spapr.c b/hw/ppc/spapr.c
> index baedadf20b8c..d063312a3b2a 100644
> --- a/hw/ppc/spapr.c
> +++ b/hw/ppc/spapr.c
> @@ -1752,7 +1752,13 @@ static void spapr_machine_reset(MachineState *machine)
> spapr_ovec_cleanup(spapr->ov5_cas);
> spapr->ov5_cas = spapr_ovec_new();
>
> - ppc_set_compat(first_ppc_cpu, spapr->max_compat_pvr, &error_fatal);
> + /*
> + * reset compat_pvr for all CPUs
> + * as qemu_devices_reset() is called before this,
> + * it can't be propagated by spapr_cpu_reset()
> + * from the first CPU to all the others
> + */
> + ppc_set_compat_all(spapr->max_compat_pvr, &error_fatal);
> }
>
> /*
> diff --git a/hw/ppc/spapr_cpu_core.c b/hw/ppc/spapr_cpu_core.c
> index bf47fbdf6f7f..45e2f2747ffc 100644
> --- a/hw/ppc/spapr_cpu_core.c
> +++ b/hw/ppc/spapr_cpu_core.c
> @@ -43,6 +43,8 @@ static void spapr_cpu_reset(void *opaque)
>
> /* Set compatibility mode to match the boot CPU, which was either set
> * by the machine reset code or by CAS. This should never fail.
> + * At startup the value is already set for all the CPUs
> + * but we need this when we hotplug a new CPU
> */
> ppc_set_compat(cpu, POWERPC_CPU(first_cpu)->compat_pvr, &error_abort);
>
--
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: 833 bytes --]
next prev parent reply other threads:[~2019-08-27 4:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 9:08 [Qemu-devel] [PATCH] pseries: Fix compat_pvr on reset Laurent Vivier
2019-08-26 9:28 ` David Gibson
2019-08-27 3:45 ` David Gibson [this message]
2019-08-28 9:02 ` Greg Kurz
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=20190827034519.GB10107@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=clg@kaod.org \
--cc=groug@kaod.org \
--cc=lvivier@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).