qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Nicholas Piggin" <npiggin@gmail.com>
To: "Maksim Kostin" <maksim.kostin@ispras.ru>, <qemu-devel@nongnu.org>
Cc: <qemu-ppc@nongnu.org>, <pavel.dovgaluk@ispras.ru>,
	<pbonzini@redhat.com>, <alex.bennee@linaro.org>,
	"Vitaly Cheptsov" <cheptsov@ispras.ru>
Subject: Re: [PATCH] hw/ppc/e500: fix broken snapshot replay
Date: Thu, 10 Aug 2023 11:34:26 +1000	[thread overview]
Message-ID: <CUOH8JPKIYFX.28OUSWNMQMQJR@wheely> (raw)
In-Reply-To: <20230809100733.32189-1-maksim.kostin@ispras.ru>

On Wed Aug 9, 2023 at 8:07 PM AEST, Maksim Kostin wrote:
> ppce500_reset_device_tree is registered for system reset, but after
> c4b075318eb1 this function rerandomizes rng-seed via
> qemu_guest_getrandom_nofail. And when loading a snapshot, it tries to read
> EVENT_RANDOM that doesn't exist, so we have an error:
>
>   qemu-system-ppc: Missing random event in the replay log
>
> To fix this, use qemu_register_reset_nosnapshotload instead of
> qemu_register_reset.

This is the same issue that spapr machine hit, so that looks good.

But is there a problem that the device tree can change after the
machine reset? In that case your snapshot could resume with a
different device tree and replay will diverge.

It looks like software could just overwrite the device tree value
in memory. That seems to be why it's rebuilt at reset time. But
maybe you could just copy the machine->fdt again.

There is also qemu_fdt_randomize_seeds that some archs use that
we might be able to use for this, if it helps.

But this is better than nothing and probably a minimal fix, so
probably good to go upstream before more complicated changes.

Thanks,
Nick

Reviewed-by: Nicholas Piggin <npiggin@gmail.com>

>
> Reported-by: Vitaly Cheptsov <cheptsov@ispras.ru>
> Fixes: c4b075318eb1 ("hw/ppc: pass random seed to fdt ")
> Resolves: https://gitlab.com/qemu-project/qemu/-/issues/1634
> Signed-off-by: Maksim Kostin <maksim.kostin@ispras.ru>
> ---
>  hw/ppc/e500.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/ppc/e500.c b/hw/ppc/e500.c
> index 67793a86f1..d5b6820d1d 100644
> --- a/hw/ppc/e500.c
> +++ b/hw/ppc/e500.c
> @@ -712,7 +712,7 @@ static int ppce500_prep_device_tree(PPCE500MachineState *machine,
>      p->kernel_base = kernel_base;
>      p->kernel_size = kernel_size;
>  
> -    qemu_register_reset(ppce500_reset_device_tree, p);
> +    qemu_register_reset_nosnapshotload(ppce500_reset_device_tree, p);
>      p->notifier.notify = ppce500_init_notify;
>      qemu_add_machine_init_done_notifier(&p->notifier);
>  



      reply	other threads:[~2023-08-10  1:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-09 10:07 [PATCH] hw/ppc/e500: fix broken snapshot replay Maksim Kostin
2023-08-10  1:34 ` Nicholas Piggin [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=CUOH8JPKIYFX.28OUSWNMQMQJR@wheely \
    --to=npiggin@gmail.com \
    --cc=alex.bennee@linaro.org \
    --cc=cheptsov@ispras.ru \
    --cc=maksim.kostin@ispras.ru \
    --cc=pavel.dovgaluk@ispras.ru \
    --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).