From: Peter Xu <peterx@redhat.com>
To: Juan Quintela <quintela@redhat.com>
Cc: qemu-devel@nongnu.org, "Yanan Wang" <wangyanan55@huawei.com>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Leonardo Bras" <leobras@redhat.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [PATCH v8 1/3] multifd: Create property multifd-flush-after-each-section
Date: Tue, 25 Apr 2023 14:42:39 -0400 [thread overview]
Message-ID: <ZEgfH1qNGV6nqpWX@x1n> (raw)
In-Reply-To: <20230425163114.2609-2-quintela@redhat.com>
On Tue, Apr 25, 2023 at 06:31:12PM +0200, Juan Quintela wrote:
> We used to flush all channels at the end of each RAM section
> sent. That is not needed, so preparing to only flush after a full
> iteration through all the RAM.
>
> Default value of the property is false. But we return "true" in
> migrate_multifd_flush_after_each_section() until we implement the code
> in following patches.
>
> Signed-off-by: Juan Quintela <quintela@redhat.com>
> Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> Signed-off-by: Juan Quintela <quintela@redhat.com>
PS: Normally I'll just keep the last Sign-off-by for each person. :)
>
> ---
>
> Rename each-iteration to after-each-section
> Rename multifd-sync-after-each-section to
> multifd-flush-after-each-section
> ---
> hw/core/machine.c | 1 +
> migration/migration.c | 13 +++++++++++++
> migration/migration.h | 13 +++++++++++++
> 3 files changed, 27 insertions(+)
>
> diff --git a/hw/core/machine.c b/hw/core/machine.c
> index 2ce97a5d3b..32bd9277b3 100644
> --- a/hw/core/machine.c
> +++ b/hw/core/machine.c
> @@ -60,6 +60,7 @@ const size_t hw_compat_7_1_len = G_N_ELEMENTS(hw_compat_7_1);
> GlobalProperty hw_compat_7_0[] = {
> { "arm-gicv3-common", "force-8-bit-prio", "on" },
> { "nvme-ns", "eui64-default", "on"},
> + { "migration", "multifd-flush-after-each-section", "on"},
> };
Here we need hw_compat_8_0 instead?
Thanks,
--
Peter Xu
next prev parent reply other threads:[~2023-04-25 18:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 16:31 [PATCH v8 0/3] Eliminate multifd flush Juan Quintela
2023-04-25 16:31 ` [PATCH v8 1/3] multifd: Create property multifd-flush-after-each-section Juan Quintela
2023-04-25 18:42 ` Peter Xu [this message]
2023-04-26 16:55 ` Juan Quintela
2023-04-25 16:31 ` [PATCH v8 2/3] multifd: Protect multifd_send_sync_main() calls Juan Quintela
2023-04-25 16:31 ` [PATCH v8 3/3] multifd: Only flush once each full round of memory Juan Quintela
2023-04-25 18:49 ` [PATCH v8 0/3] Eliminate multifd flush 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=ZEgfH1qNGV6nqpWX@x1n \
--to=peterx@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eduardo@habkost.net \
--cc=leobras@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=wangyanan55@huawei.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 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.