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>,
Gal Shachaf <galsha@mellanox.com>,
Aviad Yehezkel <aviadye@mellanox.com>
Subject: Re: [Qemu-devel] [PATCH 5/5] migration: disable RDMA WRITR after postcopy started.
Date: Thu, 12 Apr 2018 19:55:58 +0100 [thread overview]
Message-ID: <20180412185558.GJ2704@work-vm> (raw)
In-Reply-To: <CAOGPPbcF=Ln6U2UAxWFysMHAA-K08=whGQEL3FepZ+mzM4pmMg@mail.gmail.com>
* 858585 jemmy (jemmy858585@gmail.com) wrote:
> On Wed, Apr 11, 2018 at 11:56 PM, Dr. David Alan Gilbert
> <dgilbert@redhat.com> wrote:
> > * Lidong Chen (jemmy858585@gmail.com) wrote:
> >> RDMA write operations are performed with no notification to the destination
> >> qemu, then the destination qemu can not wakeup. So disable RDMA WRITE after
> >> postcopy started.
> >>
> >> Signed-off-by: Lidong Chen <lidongchen@tencent.com>
> >
> > This patch needs to be near the beginning of the series; at the moment a
> > bisect would lead you to the middle of the series which had return
> > paths, but then would fail to work properly because it would try and use
> > the RDMA code.
>
> I will fix this problem in next version.
>
> >
> >> ---
> >> migration/qemu-file.c | 3 ++-
> >> migration/rdma.c | 12 ++++++++++++
> >> 2 files changed, 14 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/migration/qemu-file.c b/migration/qemu-file.c
> >> index 8acb574..a64ac3a 100644
> >> --- a/migration/qemu-file.c
> >> +++ b/migration/qemu-file.c
> >> @@ -260,7 +260,8 @@ size_t ram_control_save_page(QEMUFile *f, ram_addr_t block_offset,
> >> int ret = f->hooks->save_page(f, f->opaque, block_offset,
> >> offset, size, bytes_sent);
> >> f->bytes_xfer += size;
> >> - if (ret != RAM_SAVE_CONTROL_DELAYED) {
> >> + if (ret != RAM_SAVE_CONTROL_DELAYED &&
> >> + ret != RAM_SAVE_CONTROL_NOT_SUPP) {
> >
> > What about f->bytes_xfer in this case?
>
> f->bytes_xfer should not update when RAM_SAVE_CONTROL_NOT_SUPP.
> I will fix this problem in next version.
>
> >
> > Is there anything we have to do at the switchover into postcopy to make
> > sure that all pages have been received?
>
> ram_save_iterate invoke ram_control_after_iterate(f, RAM_CONTROL_ROUND),
> so before next iteration which switchover into postcopy, all the pages
> sent by previous
> iteration have been received.
OK, great.
Dave
> >
> > Dave
> >
> >> if (bytes_sent && *bytes_sent > 0) {
> >> qemu_update_position(f, *bytes_sent);
> >> } else if (ret < 0) {
> >> diff --git a/migration/rdma.c b/migration/rdma.c
> >> index 81be482..8529ddd 100644
> >> --- a/migration/rdma.c
> >> +++ b/migration/rdma.c
> >> @@ -2964,6 +2964,10 @@ static size_t qemu_rdma_save_page(QEMUFile *f, void *opaque,
> >>
> >> CHECK_ERROR_STATE();
> >>
> >> + if (migrate_get_current()->state == MIGRATION_STATUS_POSTCOPY_ACTIVE) {
> >> + return RAM_SAVE_CONTROL_NOT_SUPP;
> >> + }
> >> +
> >> qemu_fflush(f);
> >>
> >> if (size > 0) {
> >> @@ -3528,6 +3532,10 @@ static int qemu_rdma_registration_start(QEMUFile *f, void *opaque,
> >>
> >> CHECK_ERROR_STATE();
> >>
> >> + if (migrate_get_current()->state == MIGRATION_STATUS_POSTCOPY_ACTIVE) {
> >> + return 0;
> >> + }
> >> +
> >> trace_qemu_rdma_registration_start(flags);
> >> qemu_put_be64(f, RAM_SAVE_FLAG_HOOK);
> >> qemu_fflush(f);
> >> @@ -3550,6 +3558,10 @@ static int qemu_rdma_registration_stop(QEMUFile *f, void *opaque,
> >>
> >> CHECK_ERROR_STATE();
> >>
> >> + if (migrate_get_current()->state == MIGRATION_STATUS_POSTCOPY_ACTIVE) {
> >> + return 0;
> >> + }
> >> +
> >> qemu_fflush(f);
> >> ret = qemu_rdma_drain_cq(f, rdma);
> >>
> >> --
> >> 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:56 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
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 [this message]
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=20180412185558.GJ2704@work-vm \
--to=dgilbert@redhat.com \
--cc=adido@mellanox.com \
--cc=aviadye@mellanox.com \
--cc=galsha@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).