All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bin Guo <guobin@linux.alibaba.com>
To: qemu-devel@nongnu.org
Cc: peterx@redhat.com, farosas@suse.de, pierrick.bouvier@oss.qualcomm.com
Subject: [PATCH 0/2] migration/postcopy: shared-fault accounting and multifd docs
Date: Tue, 15 Sep 2026 14:37:17 +0800	[thread overview]
Message-ID: <20260915063719.89031-1-guobin@linux.alibaba.com> (raw)

Two small patches from the same investigation of the postcopy
shared-page-fault path:

- Patch 1 documents that multifd and postcopy-ram can be enabled
  together since the 10.1 release, and how the two features interact.

- Patch 2 resolves the "TODO: support blocktime tracking" in
  postcopy_request_shared_page() by reporting faults taken by memory
  sharing processes (e.g. a vhost-user backend) with a foreign tid, so
  they show up in the latency reports without polluting the vCPU
  blocktime ones.

The patches are independent of each other; patch 2 was verified with a
vhost-user postcopy migration, where the shared faults now show up in
the latency reports and the page request accounting stays balanced.

Bin Guo (2):
  docs/migration: document that postcopy can be used with multifd
  migration/postcopy: account faults taken by memory sharing processes

 docs/devel/migration/postcopy.rst | 26 ++++++++++++++++++++++++++
 migration/postcopy-ram.c          | 26 ++++++++++++++++----------
 migration/postcopy-ram.h          | 10 ++++++++++
 3 files changed, 52 insertions(+), 10 deletions(-)

-- 
2.50.1 (Apple Git-155)



             reply	other threads:[~2026-09-15  6:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-15  6:37 Bin Guo [this message]
2026-09-15  6:37 ` [PATCH 1/2] docs/migration: document that postcopy can be used with multifd Bin Guo
2026-09-22 14:44   ` Fabiano Rosas
2026-09-22 17:29     ` Peter Xu
2026-09-15  6:37 ` [PATCH 2/2] migration/postcopy: account faults taken by memory sharing processes Bin Guo
2026-09-22 17:55   ` 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=20260915063719.89031-1-guobin@linux.alibaba.com \
    --to=guobin@linux.alibaba.com \
    --cc=farosas@suse.de \
    --cc=peterx@redhat.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.