From: Peter Xu <peterx@redhat.com>
To: Pawel Zmarzly <pzmarzly0@gmail.com>
Cc: qemu-devel@nongnu.org, farosas@suse.de, michel@michel-slm.name
Subject: Re: [PATCH] migration: fix parsing snapshots with x-ignore-shared flag
Date: Tue, 25 Nov 2025 14:35:26 -0500 [thread overview]
Message-ID: <aSYE_rdMhH36KBxf@x1.local> (raw)
In-Reply-To: <20251125174649.257457-1-pzmarzly0@gmail.com>
On Tue, Nov 25, 2025 at 05:46:49PM +0000, Pawel Zmarzly wrote:
> Snapshots made with mapped-ram and x-ignore-shared flags are
> not parsed properly.
>
> Signed-off-by: Pawel Zmarzly <pzmarzly0@gmail.com>
> ---
> migration/ram.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/migration/ram.c b/migration/ram.c
> index 29f016cb25..85fdc810ab 100644
> --- a/migration/ram.c
> +++ b/migration/ram.c
> @@ -4277,6 +4277,11 @@ static int parse_ramblocks(QEMUFile *f, ram_addr_t total_ram_bytes)
> id[len] = 0;
> length = qemu_get_be64(f);
>
> + if (migrate_ignore_shared()) {
> + /* Read and discard the x-ignore-shared memory region address */
> + qemu_get_be64(f);
> + }
> +
> block = qemu_ram_block_by_name(id);
> if (block) {
> ret = parse_ramblock(f, block, length);
> --
> 2.52.0
>
Thanks for the patch, though the u64 was parsed in parse_ramblock()
instead. Would you consider refactoring that function instead?
--
Peter Xu
next prev parent reply other threads:[~2025-11-25 19:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 17:46 [PATCH] migration: fix parsing snapshots with x-ignore-shared flag Pawel Zmarzly
2025-11-25 19:35 ` Peter Xu [this message]
2025-11-25 21:40 ` Fabiano Rosas
2025-11-25 22:29 ` Peter Xu
2025-11-26 12:34 ` Paweł Zmarzły
2025-11-26 12:45 ` Fabiano Rosas
2025-11-26 15:49 ` Paweł Zmarzły
2025-11-26 17:48 ` Peter Xu
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=aSYE_rdMhH36KBxf@x1.local \
--to=peterx@redhat.com \
--cc=farosas@suse.de \
--cc=michel@michel-slm.name \
--cc=pzmarzly0@gmail.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.