From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: Alexey Kardashevskiy <aik@ozlabs.ru>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org, agraf@suse.de
Subject: Re: [Qemu-devel] [RFC PATCH 2/2] target-ppc: add CPU IRQ state to PPC VMStateDescription
Date: Tue, 15 Sep 2015 22:09:54 +0100 [thread overview]
Message-ID: <55F88922.7020804@ilande.co.uk> (raw)
In-Reply-To: <55F753DE.2080003@ozlabs.ru>
On 15/09/15 00:10, Alexey Kardashevskiy wrote:
> On 09/15/2015 05:30 AM, Mark Cave-Ayland wrote:
>> Commit a90db15 "target-ppc: Convert ppc cpu savevm to VMStateDescription"
>> appears to drop the internal CPU IRQ state from the migration stream.
>> Whilst
>> testing migration on g3beige/mac99 machines, test images would
>> randomly fail to
>> resume unless a key was pressed on the VGA console.
>>
>> Further investigation suggests that internal CPU IRQ state isn't being
>> preserved and so interrupts asserted at the time of migration are
>> lost. Adding
>> the pending_interrupts and irq_input_state fields back into the migration
>> stream appears to fix the problem here during local tests.
>
> On spapr, interrupt state migrates with XICS interrupt controller and it
> resets the CPU bits you are adding to the migration descriptor. I'd
> expect openpic (this one is used for mac99?) to do the same.
Interesting. I wrote the patch that converted openpic to
VMStateDescription at the end of last year, and my understanding from
the feedback was that ideally interrupt state should be maintained so
that no post_load function was required. I guess spapr is very different
from the basic Mac machines though.
Also I see that you also removed the reference to cpu_write_xer() which
appears to set some related internal state variables. Is this now not
necessary either?
>>
>> Signed-off-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
>> ---
>> target-ppc/machine.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/target-ppc/machine.c b/target-ppc/machine.c
>> index bd99844..968a7d6 100644
>> --- a/target-ppc/machine.c
>> +++ b/target-ppc/machine.c
>> @@ -528,6 +528,8 @@ const VMStateDescription vmstate_ppc_cpu = {
>>
>> /* Internal state */
>> VMSTATE_UINTTL(env.hflags_nmsr, PowerPCCPU),
>> + VMSTATE_UINT32(env.pending_interrupts, PowerPCCPU),
>> + VMSTATE_UINT32(env.irq_input_state, PowerPCCPU),
>
> This update requires a "version" increment for vmstate_ppc_cpu and
> VMSTATE_UINT32_V instead of VMSTATE_UINT32.
So this means you're happy with the basic patch if I go ahead and make
the version changes too?
ATB,
Mark.
next prev parent reply other threads:[~2015-09-15 21:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 19:30 [Qemu-devel] [RFC PATCH 0/2] target-ppc migration fixes Mark Cave-Ayland
2015-09-14 19:30 ` [Qemu-devel] [RFC PATCH 1/2] target-ppc: remove hreg_compute_mem_idx() from cpu_post_load Mark Cave-Ayland
2015-09-14 23:25 ` Alexey Kardashevskiy
2015-09-14 19:30 ` [Qemu-devel] [RFC PATCH 2/2] target-ppc: add CPU IRQ state to PPC VMStateDescription Mark Cave-Ayland
2015-09-14 23:10 ` Alexey Kardashevskiy
2015-09-15 21:09 ` Mark Cave-Ayland [this message]
2015-09-17 4:32 ` Alexey Kardashevskiy
2015-09-20 20:31 ` [Qemu-devel] [RFC PATCH 0/2] target-ppc migration fixes Alexander Graf
2015-10-23 1:46 ` david
2015-10-23 19:22 ` Mark Cave-Ayland
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=55F88922.7020804@ilande.co.uk \
--to=mark.cave-ayland@ilande.co.uk \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.