From: Fabiano Rosas <farosas@suse.de>
To: marcandre.lureau@redhat.com, qemu-devel@nongnu.org
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>,
"John Snow" <jsnow@redhat.com>, "Cleber Rosa" <crosa@redhat.com>
Subject: Re: [PATCH] analyze-migration: ignore RAM_SAVE_FLAG_MULTIFD_FLUSH
Date: Wed, 27 Sep 2023 16:58:58 -0300 [thread overview]
Message-ID: <87ttrfqtfh.fsf@suse.de> (raw)
In-Reply-To: <20230926081819.433631-1-marcandre.lureau@redhat.com>
marcandre.lureau@redhat.com writes:
> From: Marc-André Lureau <marcandre.lureau@redhat.com>
>
> Traceback (most recent call last):
> File "scripts/analyze-migration.py", line 605, in <module>
> dump.read(dump_memory = args.memory)
> File "scripts/analyze-migration.py", line 542, in read
> section.read()
> File "scripts/analyze-migration.py", line 214, in read
> raise Exception("Unknown RAM flags: %x" % flags)
> Exception: Unknown RAM flags: 200
>
> See commit 77c259a4cb ("multifd: Create property multifd-flush-after-each-section")
>
> Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Reviewed-by: Fabiano Rosas <farosas@suse.de>
This is the second time this FLUSH flag has caused issues. If I figure
out how to make meson copy the script to the build dir I could add a
test for this to migration-test.c.
prev parent reply other threads:[~2023-09-27 20:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 8:18 [PATCH] analyze-migration: ignore RAM_SAVE_FLAG_MULTIFD_FLUSH marcandre.lureau
2023-09-27 10:32 ` Marc-André Lureau
2023-10-03 21:08 ` Peter Xu
2023-09-27 19:58 ` Fabiano Rosas [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=87ttrfqtfh.fsf@suse.de \
--to=farosas@suse.de \
--cc=crosa@redhat.com \
--cc=jsnow@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@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.