From: Ivan Ren <renyime@gmail.com>
To: quintela@redhat.com, dgilbert@redhat.com
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/3] migration: fix migrate_cancel problems of multifd
Date: Sun, 14 Jul 2019 22:53:05 +0800 [thread overview]
Message-ID: <CA+6E1==9SCRd4aVm0_M7gHbMNPhVsBExof4+DeDCGiFDZwkpMA@mail.gmail.com> (raw)
In-Reply-To: <1561468699-9819-1-git-send-email-ivanren@tencent.com>
The problem still exists in mainline, Ping for review
On Tue, Jun 25, 2019 at 9:18 PM Ivan Ren <renyime@gmail.com> wrote:
> The patches fix the problems encountered in multifd migration when try
> to cancel the migration by migrate_cancel.
>
> Ivan Ren (3):
> migration: fix migrate_cancel leads live_migration thread endless loop
> migration: fix migrate_cancel leads live_migration thread hung forever
> migration: fix migrate_cancel multifd migration leads destination hung
> forever
>
> migration/ram.c | 62 ++++++++++++++++++++++++++++++++++++++++---------
> 1 file changed, 51 insertions(+), 11 deletions(-)
>
> --
> 2.17.2 (Apple Git-113)
>
>
prev parent reply other threads:[~2019-07-14 14:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 13:18 [Qemu-devel] [PATCH 0/3] migration: fix migrate_cancel problems of multifd Ivan Ren
2019-06-25 13:18 ` [Qemu-devel] [PATCH 1/3] migration: fix migrate_cancel leads live_migration thread endless loop Ivan Ren
2019-07-24 8:43 ` Juan Quintela
2019-06-25 13:18 ` [Qemu-devel] [PATCH 2/3] migration: fix migrate_cancel leads live_migration thread hung forever Ivan Ren
2019-07-24 8:47 ` Juan Quintela
2019-07-24 9:18 ` Juan Quintela
2019-06-25 13:18 ` [Qemu-devel] [PATCH 3/3] migration: fix migrate_cancel multifd migration leads destination " Ivan Ren
2019-07-24 7:01 ` Ivan Ren
2019-07-24 9:01 ` Juan Quintela
2019-07-24 11:30 ` Ivan Ren
2019-07-14 14:53 ` Ivan Ren [this message]
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='CA+6E1==9SCRd4aVm0_M7gHbMNPhVsBExof4+DeDCGiFDZwkpMA@mail.gmail.com' \
--to=renyime@gmail.com \
--cc=dgilbert@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).