From: Bin Guo <guobin@linux.alibaba.com>
To: qemu-devel@nongnu.org
Cc: peterx@redhat.com, farosas@suse.de
Subject: [PATCH 0/8] migration: cleanups, fixes and micro-optimizations
Date: Mon, 18 May 2026 19:01:04 +0800 [thread overview]
Message-ID: <20260518110112.21395-1-guobin@linux.alibaba.com> (raw)
This series collects several small improvements to the migration
subsystem:
- Bug fix: off-by-one in multifd recv channel ID validation that
could allow an out-of-bounds write (patch 5).
- Micro-optimizations: cache migrate_multifd_channels() in hot
paths (patches 7-8), use stack-allocated bitmap instead of
heap (patch 4), avoid per-element heap churn in vmstate ptr
marker field (patch 3).
- Cleanups: collapse migration_fd_valid into a single boolean
expression (patch 1), replace strcpy("") with explicit NUL
termination (patch 2), merge thread-join and cleanup loops in
multifd_recv_cleanup (patch 6).
No functional change intended except for the off-by-one fix in
patch 5.
Bin Guo (8):
migration/fd: collapse migration_fd_valid into single boolean
expression
migration/global_state: replace strcpy("") with explicit NUL
termination
migration/vmstate: avoid per-element heap churn in vmsd ptr marker
field
migration/savevm: use stack-allocated bitmap in
configuration_validate_capabilities
migration/multifd: fix off-by-one in recv channel ID validation
migration/multifd: merge thread-join and cleanup loops in
multifd_recv_cleanup
migration/multifd: cache migrate_multifd_channels() in send/recv hot
paths
migration/multifd: cache channel count in multifd_send_sync_main
migration/fd.c | 10 +---------
migration/global_state.c | 2 +-
migration/multifd.c | 32 +++++++++++++++++--------------
migration/savevm.c | 5 ++---
migration/vmstate.c | 41 ++++++++++++++++------------------------
5 files changed, 38 insertions(+), 52 deletions(-)
--
2.50.1 (Apple Git-155)
next reply other threads:[~2026-05-18 11:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 11:01 Bin Guo [this message]
2026-05-18 11:01 ` [PATCH 1/8] migration/fd: collapse migration_fd_valid into single boolean expression Bin Guo
2026-05-18 20:22 ` Fabiano Rosas
2026-05-18 11:01 ` [PATCH 2/8] migration/global_state: replace strcpy("") with explicit NUL termination Bin Guo
2026-05-18 20:32 ` Fabiano Rosas
2026-05-18 11:01 ` [PATCH 3/8] migration/vmstate: avoid per-element heap churn in vmsd ptr marker field Bin Guo
2026-05-19 7:32 ` Fabiano Rosas
2026-05-18 11:01 ` [PATCH 4/8] migration/savevm: use stack-allocated bitmap in configuration_validate_capabilities Bin Guo
2026-05-18 20:53 ` Fabiano Rosas
2026-05-18 11:01 ` [PATCH 5/8] migration/multifd: fix off-by-one in recv channel ID validation Bin Guo
2026-05-18 19:43 ` Fabiano Rosas
2026-05-18 11:01 ` [PATCH 6/8] migration/multifd: merge thread-join and cleanup loops in multifd_recv_cleanup Bin Guo
2026-05-18 20:21 ` Fabiano Rosas
2026-05-18 11:01 ` [PATCH 7/8] migration/multifd: cache migrate_multifd_channels() in send/recv hot paths Bin Guo
2026-05-19 7:16 ` Fabiano Rosas
2026-05-18 11:01 ` [PATCH 8/8] migration/multifd: cache channel count in multifd_send_sync_main Bin Guo
2026-05-19 7:17 ` Fabiano Rosas
2026-05-20 19:33 ` [PATCH 0/8] migration: cleanups, fixes and micro-optimizations Peter Xu
-- strict thread matches above, loose matches on Subject: below --
2026-05-18 10:51 Bin Guo
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=20260518110112.21395-1-guobin@linux.alibaba.com \
--to=guobin@linux.alibaba.com \
--cc=farosas@suse.de \
--cc=peterx@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.