From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Cc: Leonardo Bras <leobras@redhat.com>, Peter Xu <peterx@redhat.com>,
Fabiano Rosas <farosas@suse.de>,
Juan Quintela <quintela@redhat.com>
Subject: [PATCH 0/1] migration: Fix non-multifd migration
Date: Wed, 11 Oct 2023 22:55:47 +0200 [thread overview]
Message-ID: <20231011205548.10571-1-quintela@redhat.com> (raw)
Fix sending multifd sync packets when not multifd is seleceted.
Basically we were using:
if (migrate_multifd_flush_after_each_iteration()) { ...}
and
if (!migrate_multifd_flush_after_each_iteration()) { ...}
But that is not enough for non multifd migration, so changed to also
check first if migrate_multid() is enabled in each test.
Please, review.
Juan Quintela (1):
migration: Non multifd migration don't care about multifd flushes
migration/ram.c | 14 ++++++++------
1 file changed, 8 insertions(+), 6 deletions(-)
--
2.41.0
next reply other threads:[~2023-10-11 20:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 20:55 Juan Quintela [this message]
2023-10-11 20:55 ` [PATCH 1/1] migration: Non multifd migration don't care about multifd flushes Juan Quintela
2023-10-12 1:14 ` Zhijian Li (Fujitsu)
2023-10-12 13:03 ` 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=20231011205548.10571-1-quintela@redhat.com \
--to=quintela@redhat.com \
--cc=farosas@suse.de \
--cc=leobras@redhat.com \
--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 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).