All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Aadeshveer Singh <aadeshveer07@gmail.com>
Cc: qemu-devel@nongnu.org, farosas@suse.de, pbonzini@redhat.com,
	philmd@mailo.com, lvivier@redhat.com, ayoub@saferwall.com,
	pierrick.bouvier@oss.qualcomm.com
Subject: Re: [PATCH v5 00/11] migration: fast snapshot load
Date: Tue, 18 Aug 2026 13:45:42 -0400	[thread overview]
Message-ID: <aoSaRoZoke2WjSRX@x1.local> (raw)
In-Reply-To: <20260816174631.1547811-1-aadeshveer07@gmail.com>

Hey, Aadeshveer,

On Sun, Aug 16, 2026 at 11:16:20PM +0530, Aadeshveer Singh wrote:
> v4 -> v5
> - Modify pending_bmap(Patch 6) to use variable size for better
>   efficient atomic state management
> - Added a comment(Patch 7) explaining postcopy_mapped_ram_load_page
>   explaining why cases where guest page is larger than host page are
>   disabled following what remote postcopy follows
> - Add a new check(Patch 9) in migrate_prepare to bail out if migrate
>   was used with fast snapshot load enabled, as suggested by Peter

There're something you didn't mention but we discussed it only during the
meeting about host/guest psize problem.  For this time, I'll do it for you.
Aadeshveer, please remember to mention such conclusions and findings in the
future when you will be working on other patches.

The quick summary: Aadeshveer found postcopy doesn't support guest psize >
host psize since the start, which will already fail the set capabilities in
postcopy_ram_supported_by_host().  It means we can also skip supporting
that in fast snapshot load.

Personally, I still prefer removal of all such guest psize > host psize
handlings in your current code; postcopy_place_page() isn't ready, so the
current code won't work anyway for that setup.  With it removed, then we
can stick pending_bmap with host psize, which can also cause less confusion
and make it easier to read.  But I think it's not a huge deal, and AFAIU
the code works as expected.  So I think it's fine for now.

If you're going to prepare a small series on top of this, please consider
reverting those changes back to the simple version with one patch on top.

Other than that, thanks for your hard work in the past few months!  Since I
believe this code still should function all well, I queued it for 11.2.

-- 
Peter Xu



      parent reply	other threads:[~2026-08-18 17:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-16 17:46 [PATCH v5 00/11] migration: fast snapshot load Aadeshveer Singh
2026-08-16 17:46 ` [PATCH v5 01/11] migration: Propagate error in postcopy setup functions Aadeshveer Singh
2026-08-16 17:46 ` [PATCH v5 02/11] migration: Extract blocktime marking helper Aadeshveer Singh
2026-08-16 17:46 ` [PATCH v5 03/11] migration: Rename postcopy_listen_thread_bh Aadeshveer Singh
2026-08-16 17:46 ` [PATCH v5 04/11] migration: Use file_bmap for RAMBlock during incoming file load Aadeshveer Singh
2026-08-16 17:46 ` [PATCH v5 05/11] migration: Make qemu_get_buffer_at() thread-safe Aadeshveer Singh
2026-08-16 17:46 ` [PATCH v5 06/11] migration: add RAMBlock field and helper for fast snapshot load Aadeshveer Singh
2026-08-16 17:46 ` [PATCH v5 07/11] migration: add support for fault thread to load pages from disk Aadeshveer Singh
2026-08-16 17:46 ` [PATCH v5 08/11] migration: add eager load thread and setup for fast snapshot load Aadeshveer Singh
2026-08-16 17:46 ` [PATCH v5 09/11] migration: update capability conflict test for postcopy-ram+mapped-ram Aadeshveer Singh
2026-08-16 17:46 ` [PATCH v5 10/11] migration/tests: Add test for fast snapshot load Aadeshveer Singh
2026-08-16 17:46 ` [PATCH v5 11/11] docs/migration: Add documentation for fast snapshot load feature Aadeshveer Singh
2026-08-18 17:45 ` Peter Xu [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=aoSaRoZoke2WjSRX@x1.local \
    --to=peterx@redhat.com \
    --cc=aadeshveer07@gmail.com \
    --cc=ayoub@saferwall.com \
    --cc=farosas@suse.de \
    --cc=lvivier@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@mailo.com \
    --cc=pierrick.bouvier@oss.qualcomm.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.