From: David Gibson <david@gibson.dropbear.id.au>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org, aik@ozlabs.ru,
lvivier@redhat.com
Subject: Re: [Qemu-devel] [PATCH 3/4] ppc: add CPU access_type into the migration stream
Date: Mon, 11 Sep 2017 20:57:29 +1000 [thread overview]
Message-ID: <20170911105729.GC2784@umbus.fritz.box> (raw)
In-Reply-To: <1505054255-2990-4-git-send-email-mark.cave-ayland@ilande.co.uk>
[-- Attachment #1: Type: text/plain, Size: 1596 bytes --]
On Sun, Sep 10, 2017 at 03:37:34PM +0100, Mark Cave-Ayland wrote:
> This is referenced in cpu_ppc_handle_mmu_fault() and so should be included
> in the migration stream.
That is not, on its own, sufficient reason.
> Note: the vmstate_ppc version number has already been bumped by the previous
> patch in this series.
>
> Signed-off-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
As with 2/4 it breaks backwards migration.
But more, I really disklike the idea of migrating this. It's internal
state for one, and it's also essentially transitory state. Can we
avoid putting it in the otherwise persistent structure at all? Can we
derive the state from elsewhere? Can we prevent migration from
occurring in the small windows where this data is live?
> ---
> target/ppc/machine.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/target/ppc/machine.c b/target/ppc/machine.c
> index 8fec1a4..10b3c41 100644
> --- a/target/ppc/machine.c
> +++ b/target/ppc/machine.c
> @@ -676,7 +676,7 @@ const VMStateDescription vmstate_ppc_cpu = {
>
> /* Internal state */
> VMSTATE_UINTTL(env.hflags_nmsr, PowerPCCPU),
> - /* FIXME: access_type? */
> + VMSTATE_UINT8_V(env.access_type, PowerPCCPU, 6),
>
> /* Interrupt state */
> VMSTATE_UINT32_V(env.pending_interrupts, PowerPCCPU, 6),
--
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:[~2017-09-11 10:57 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-10 14:37 [Qemu-devel] [PATCH 0/4] ppc: migration fixes for TCG Mark Cave-Ayland
2017-09-10 14:37 ` [Qemu-devel] [PATCH 1/4] ppc: change CPUPPCState access_type from int to uint8_t Mark Cave-Ayland
2017-09-10 16:30 ` Laurent Vivier
2017-09-10 18:00 ` Mark Cave-Ayland
2017-09-10 14:37 ` [Qemu-devel] [PATCH 2/4] ppc: add CPU IRQ state to PPC VMStateDescription Mark Cave-Ayland
2017-09-11 7:50 ` [Qemu-devel] [Qemu-ppc] " Greg Kurz
2017-09-11 9:30 ` Dr. David Alan Gilbert
2017-09-11 10:48 ` David Gibson
2017-09-11 16:46 ` Mark Cave-Ayland
2017-09-11 17:19 ` Dr. David Alan Gilbert
2017-09-13 7:03 ` David Gibson
2017-09-12 16:21 ` Dr. David Alan Gilbert
2017-09-12 16:41 ` Mark Cave-Ayland
2017-09-12 16:46 ` Mark Cave-Ayland
2017-09-13 2:23 ` Alexey Kardashevskiy
2017-09-13 6:02 ` David Gibson
2017-09-13 16:44 ` Mark Cave-Ayland
2017-09-13 17:13 ` Greg Kurz
2017-09-14 3:48 ` David Gibson
2017-09-14 3:30 ` David Gibson
2017-09-10 14:37 ` [Qemu-devel] [PATCH 3/4] ppc: add CPU access_type into the migration stream Mark Cave-Ayland
2017-09-11 10:57 ` David Gibson [this message]
2017-09-11 16:52 ` Mark Cave-Ayland
2017-09-13 7:19 ` David Gibson
2017-09-13 17:17 ` Mark Cave-Ayland
2017-09-14 3:54 ` David Gibson
2017-09-10 14:37 ` [Qemu-devel] [PATCH 4/4] ppc: ensure we update the decrementer value during migration Mark Cave-Ayland
2017-09-13 7:12 ` David Gibson
2017-09-13 17:11 ` Mark Cave-Ayland
2017-09-13 17:58 ` Laurent Vivier
2017-09-14 3:52 ` David Gibson
2017-09-15 12:45 ` Mark Cave-Ayland
2017-09-19 8:36 ` David Gibson
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=20170911105729.GC2784@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=aik@ozlabs.ru \
--cc=lvivier@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--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).