From: Juan Quintela <quintela@redhat.com>
To: Wei Yang <richardw.yang@linux.intel.com>
Cc: dgilbert@redhat.com, qemu-devel@nongnu.org
Subject: Re: [PATCH 0/2] not use multifd during postcopy
Date: Thu, 09 Jan 2020 10:50:25 +0100 [thread overview]
Message-ID: <87v9plyn4u.fsf@secure.laptop> (raw)
In-Reply-To: <20200106012640.GA15834@richard> (Wei Yang's message of "Mon, 6 Jan 2020 09:26:40 +0800")
Wei Yang <richardw.yang@linux.intel.com> wrote:
> On Mon, Dec 16, 2019 at 10:35:39AM +0800, Wei Yang wrote:
>>Would this one be picked up this time?
>
> Happy new year to all.
>
> Can I ask the plan for this patch set?
queued
>
>>
>>On Sat, Oct 26, 2019 at 07:19:58AM +0800, Wei Yang wrote:
>>>We don't support multifd during postcopy, but user still could enable
>>>both multifd and postcopy. This leads to migration failure.
>>>
>>>Patch 1 does proper cleanup, otherwise we may have data corruption.
>>>Patch 2 does the main job.
>>>
>>>BTW, current multifd synchronization method needs a cleanup. Will send another
>>>patch set.
>>>
>>>Wei Yang (2):
>>> migration/multifd: clean pages after filling packet
>>> migration/multifd: not use multifd during postcopy
>>>
>>> migration/ram.c | 15 ++++++++++-----
>>> 1 file changed, 10 insertions(+), 5 deletions(-)
>>>
>>>--
>>>2.17.1
>>
>>--
>>Wei Yang
>>Help you, Help me
next prev parent reply other threads:[~2020-01-09 9:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 23:19 [PATCH 0/2] not use multifd during postcopy Wei Yang
2019-10-25 23:19 ` [PATCH 1/2] migration/multifd: clean pages after filling packet Wei Yang
2019-11-19 10:54 ` Juan Quintela
2019-10-25 23:20 ` [PATCH 2/2] migration/multifd: not use multifd during postcopy Wei Yang
2019-11-19 10:55 ` Juan Quintela
2019-11-20 0:35 ` Wei Yang
2019-11-18 1:48 ` [PATCH 0/2] " Wei Yang
2019-12-16 2:35 ` Wei Yang
2020-01-06 1:26 ` Wei Yang
2020-01-09 9:50 ` Juan Quintela [this message]
2020-01-10 2:31 ` Wei Yang
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=87v9plyn4u.fsf@secure.laptop \
--to=quintela@redhat.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richardw.yang@linux.intel.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).