From: David Hildenbrand <david@redhat.com>
To: Steve Sistare <steven.sistare@oracle.com>, qemu-devel@nongnu.org
Cc: Peter Xu <peterx@redhat.com>, Fabiano Rosas <farosas@suse.de>,
Philippe Mathieu-Daude <philmd@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH V4] migration: ram block cpr blockers
Date: Tue, 25 Feb 2025 22:10:54 +0100 [thread overview]
Message-ID: <28175337-552e-45c3-b6db-86c8f06fbce8@redhat.com> (raw)
In-Reply-To: <1740517563-245516-1-git-send-email-steven.sistare@oracle.com>
> + /* Ram device is remapped in new QEMU */
> + if (memory_region_is_ram_device(mr)) {
> + return true;
> + }
> +
> + /* Named files are remapped in new QEMU, same contents if shared (no COW) */
> + if (qemu_ram_is_shared(rb) && qemu_ram_is_named_file(rb)) {
> + return true;
> + }
> +
> + /* A file descriptor is remapped in new QEMU */
> + if (rb->fd >= 0 && qemu_ram_is_shared(rb)) {
> + return true;
> + }
Sorry, I was not fast enough to reply to your v3 reply.
This is now essentially:
if (qemu_ram_is_shared(rb) &&
(qemu_ram_is_named_file(rb) || rb->fd >= 0)) {
return true;
}
But what is the purpose of the "name file" check then, if rb->fd
essentially allows for any files?
So either the "fd >= 0" check is insufficient or the
qemu_ram_is_named_file() check us superfluous.
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-02-25 21:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 21:06 [PATCH V4] migration: ram block cpr blockers Steve Sistare
2025-02-25 21:10 ` David Hildenbrand [this message]
2025-02-26 13:29 ` Steven Sistare
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=28175337-552e-45c3-b6db-86c8f06fbce8@redhat.com \
--to=david@redhat.com \
--cc=farosas@suse.de \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=steven.sistare@oracle.com \
/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).