From: Juan Quintela <quintela@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: Li Zhijian <lizhijian@fujitsu.com>,
leobras@redhat.com, qemu-devel@nongnu.org,
Fabiano Rosas <farosas@suse.de>
Subject: Re: [PATCH v2 1/2] migration: Fix rdma migration failed
Date: Wed, 18 Oct 2023 16:32:45 +0200 [thread overview]
Message-ID: <87a5sg80he.fsf@secure.mitica> (raw)
In-Reply-To: <ZSAtKmOFkomgXyJ7@x1n> (Peter Xu's message of "Fri, 6 Oct 2023 11:52:10 -0400")
I see in upstream already:
(master)$ g branch --show-current
master
(master)$ g branch --contains d4f34485ca8a077c98fc2303451e9bece9200dd7
* master
(master)$
commit d4f34485ca8a077c98fc2303451e9bece9200dd7
Author: Juan Quintela <quintela@redhat.com>
Date: Wed Oct 11 22:55:48 2023 +0200
migration: Non multifd migration don't care about multifd flushes
RDMA was having trouble because
migrate_multifd_flush_after_each_section() can only be true or false,
but we don't want to send any flush when we are not in multifd
migration.
CC: Fabiano Rosas <farosas@suse.de
Fixes: 294e5a4034e81 ("multifd: Only flush once each full round of memory")
Reported-by: Li Zhijian <lizhijian@fujitsu.com>
Reviewed-by: Li Zhijian <lizhijian@fujitsu.com>
Reviewed-by: Peter Xu <peterx@redhat.com>
Signed-off-by: Juan Quintela <quintela@redhat.com>
Message-ID: <20231011205548.10571-2-quintela@redhat.com>
Or I am missing something?
Later, Juan.
next prev parent reply other threads:[~2023-10-18 14:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 10:01 [PATCH v2 1/2] migration: Fix rdma migration failed Li Zhijian
2023-09-26 10:01 ` [PATCH v2 2/2] migration/rdma: zore out head.repeat to make the error more clear Li Zhijian
2023-10-03 18:57 ` Juan Quintela
2023-09-26 17:04 ` [PATCH v2 1/2] migration: Fix rdma migration failed Peter Xu
2023-10-03 19:00 ` Juan Quintela
2023-10-03 18:57 ` Juan Quintela
2023-10-06 15:52 ` Peter Xu
2023-10-06 17:15 ` Peter Xu
2023-10-18 14:32 ` Juan Quintela [this message]
2023-10-07 6:03 ` Zhijian Li (Fujitsu)
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=87a5sg80he.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=farosas@suse.de \
--cc=leobras@redhat.com \
--cc=lizhijian@fujitsu.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 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.