From: Lukas Straub <lukasstraub2@web.de>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: Juan Quintela <quintela@redhat.com>, Peter Xu <peterx@redhat.com>,
Leonardo Bras <leobras@redhat.com>
Subject: [PATCH 0/5] multifd: Add colo support
Date: Mon, 8 May 2023 02:51:43 +0200 [thread overview]
Message-ID: <cover.1683506133.git.lukasstraub2@web.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 835 bytes --]
Hello Everyone,
These patches add support for colo to multifd.
Lukas Straub (5):
ram: Add public helper to set colo bitmap
ram: Let colo_flush_ram_cache take the bitmap_mutex
multifd: Introduce multifd-internal.h
multifd: Introduce a overridable revc_pages method
multifd: Add colo support
migration/meson.build | 1 +
migration/multifd-colo.c | 67 ++++++++++++++++++++++++++++++++
migration/multifd-internal.h | 39 +++++++++++++++++++
migration/multifd.c | 74 +++++++++++++++++++++++-------------
migration/multifd.h | 2 +
migration/ram.c | 19 +++++++--
migration/ram.h | 1 +
7 files changed, 173 insertions(+), 30 deletions(-)
create mode 100644 migration/multifd-colo.c
create mode 100644 migration/multifd-internal.h
--
2.39.2
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2023-05-08 0:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 0:51 Lukas Straub [this message]
2023-05-08 0:52 ` [PATCH 1/5] ram: Add public helper to set colo bitmap Lukas Straub
2023-05-08 0:52 ` [PATCH 2/5] ram: Let colo_flush_ram_cache take the bitmap_mutex Lukas Straub
2023-05-08 0:52 ` [PATCH 3/5] multifd: Introduce multifd-internal.h Lukas Straub
2023-05-08 0:52 ` [PATCH 4/5] multifd: Introduce a overridable revc_pages method Lukas Straub
2023-05-08 0:52 ` [PATCH 5/5] multifd: Add colo support Lukas Straub
2023-05-08 15:13 ` Juan Quintela
2023-05-08 1:38 ` [PATCH 0/5] " 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=cover.1683506133.git.lukasstraub2@web.de \
--to=lukasstraub2@web.de \
--cc=leobras@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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).