From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: 858585 jemmy <jemmy858585@gmail.com>
Cc: Juan Quintela <quintela@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
adido@mellanox.com, licq@mellanox.com,
Lidong Chen <lidongchen@tencent.com>
Subject: Re: [Qemu-devel] [PATCH 4/5] migration: fix qemu carsh when RDMA live migration
Date: Thu, 12 Apr 2018 19:58:02 +0100 [thread overview]
Message-ID: <20180412185801.GK2704@work-vm> (raw)
In-Reply-To: <CAOGPPbfVN2gz95Tsj4Vs1LzJcMbkda0_6=+sC_5g+WG8Hg3KNg@mail.gmail.com>
* 858585 jemmy (jemmy858585@gmail.com) wrote:
> On Thu, Apr 12, 2018 at 12:43 AM, Dr. David Alan Gilbert
> <dgilbert@redhat.com> wrote:
> > * Lidong Chen (jemmy858585@gmail.com) wrote:
> >> After postcopy, the destination qemu work in the dedicated
> >> thread, so only invoke yield_until_fd_readable before postcopy
> >> migration.
> >
> > The subject line needs to be more discriptive:
> > migration: Stop rdma yielding during incoming postcopy
> >
> > I think.
> > (Also please check the subject spellings)
> >
> >> Signed-off-by: Lidong Chen <lidongchen@tencent.com>
> >> ---
> >> migration/rdma.c | 4 +++-
> >> 1 file changed, 3 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/migration/rdma.c b/migration/rdma.c
> >> index 53773c7..81be482 100644
> >> --- a/migration/rdma.c
> >> +++ b/migration/rdma.c
> >> @@ -1489,11 +1489,13 @@ static int qemu_rdma_wait_comp_channel(RDMAContext *rdma)
> >> * Coroutine doesn't start until migration_fd_process_incoming()
> >> * so don't yield unless we know we're running inside of a coroutine.
> >> */
> >> - if (rdma->migration_started_on_destination) {
> >> + if (rdma->migration_started_on_destination &&
> >> + migration_incoming_get_current()->state == MIGRATION_STATUS_ACTIVE) {
> >
> > OK, that's a bit delicate; watch if it ever gets called in a failure
> > case or similar - and also wathc out if we make more use of the status
> > on the destination, but otherwise, and with a fix for the subject;
>
> How about use migration_incoming_get_current()->have_listen_thread?
That's supposed to be pretty internal to the postcopy code, so I prefer
the status check.
Dave
> if (rdma->migration_started_on_destination &&
> migration_incoming_get_current()->have_listen_thread == false) {
> yield_until_fd_readable(rdma->comp_channel->fd);
> }
>
> >
> >
> > Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> >
> >> yield_until_fd_readable(rdma->comp_channel->fd);
> >> } else {
> >> /* This is the source side, we're in a separate thread
> >> * or destination prior to migration_fd_process_incoming()
> >> + * after postcopy, the destination also in a seprate thread.
> >> * we can't yield; so we have to poll the fd.
> >> * But we need to be able to handle 'cancel' or an error
> >> * without hanging forever.
> >> --
> >> 1.8.3.1
> >>
> > --
> > Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2018-04-12 18:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-07 8:26 [Qemu-devel] [PATCH 0/5] Enable postcopy RDMA live migration Lidong Chen
2018-04-07 8:26 ` [Qemu-devel] [PATCH 1/5] migration: create a dedicated connection for rdma return path Lidong Chen
2018-04-11 16:57 ` Dr. David Alan Gilbert
2018-04-07 8:26 ` [Qemu-devel] [PATCH 2/5] migration: add the interface to set get_return_path Lidong Chen
2018-04-11 17:18 ` Dr. David Alan Gilbert
2018-04-12 8:28 ` Daniel P. Berrangé
2018-04-12 10:08 ` 858585 jemmy
2018-04-07 8:26 ` [Qemu-devel] [PATCH 3/5] migration: implement the get_return_path for RDMA iochannel Lidong Chen
2018-04-07 8:26 ` [Qemu-devel] [PATCH 4/5] migration: fix qemu carsh when RDMA live migration Lidong Chen
2018-04-11 16:43 ` Dr. David Alan Gilbert
2018-04-12 9:40 ` 858585 jemmy
2018-04-12 18:58 ` Dr. David Alan Gilbert [this message]
2018-04-07 8:26 ` [Qemu-devel] [PATCH 5/5] migration: disable RDMA WRITR after postcopy started Lidong Chen
2018-04-11 15:56 ` Dr. David Alan Gilbert
2018-04-12 6:50 ` 858585 jemmy
2018-04-12 18:55 ` Dr. David Alan Gilbert
2018-04-09 1:05 ` [Qemu-devel] [PATCH 0/5] Enable postcopy RDMA live migration 858585 jemmy
2018-04-11 12:29 ` Dr. David Alan Gilbert
2018-04-12 3:57 ` 858585 jemmy
2018-04-24 13:36 ` Dr. David Alan Gilbert
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=20180412185801.GK2704@work-vm \
--to=dgilbert@redhat.com \
--cc=adido@mellanox.com \
--cc=jemmy858585@gmail.com \
--cc=licq@mellanox.com \
--cc=lidongchen@tencent.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).