From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:45979) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fT6hh-0005Ts-6n for qemu-devel@nongnu.org; Wed, 13 Jun 2018 10:24:54 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fT6hc-0008Ci-SQ for qemu-devel@nongnu.org; Wed, 13 Jun 2018 10:24:53 -0400 Received: from mx3-rdu2.redhat.com ([66.187.233.73]:49440 helo=mx1.redhat.com) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fT6hc-0008BX-MU for qemu-devel@nongnu.org; Wed, 13 Jun 2018 10:24:48 -0400 Date: Wed, 13 Jun 2018 15:24:44 +0100 From: "Dr. David Alan Gilbert" Message-ID: <20180613142443.GF2676@work-vm> References: <1528212489-19137-1-git-send-email-lidongchen@tencent.com> <1528212489-19137-10-git-send-email-lidongchen@tencent.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1528212489-19137-10-git-send-email-lidongchen@tencent.com> Subject: Re: [Qemu-devel] [PATCH v5 09/10] migration: poll the cm event while wait RDMA work request completion List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Lidong Chen Cc: zhang.zhanghailiang@huawei.com, quintela@redhat.com, berrange@redhat.com, aviadye@mellanox.com, pbonzini@redhat.com, qemu-devel@nongnu.org, adido@mellanox.com, galsha@mellanox.com, Lidong Chen * Lidong Chen (jemmy858585@gmail.com) wrote: > If the peer qemu is crashed, the qemu_rdma_wait_comp_channel function > maybe loop forever. so we should also poll the cm event fd, and when > receive RDMA_CM_EVENT_DISCONNECTED and RDMA_CM_EVENT_DEVICE_REMOVAL, > we consider some error happened. > > Signed-off-by: Lidong Chen Was there a reply which explained/pointed to docs for cm_event? Or a Review-by from one of the Infiniband people would be fine. Dave > --- > migration/rdma.c | 33 ++++++++++++++++++++++++++++++--- > 1 file changed, 30 insertions(+), 3 deletions(-) > > diff --git a/migration/rdma.c b/migration/rdma.c > index f12e8d5..bb6989e 100644 > --- a/migration/rdma.c > +++ b/migration/rdma.c > @@ -1489,6 +1489,9 @@ static uint64_t qemu_rdma_poll(RDMAContext *rdma, uint64_t *wr_id_out, > */ > static int qemu_rdma_wait_comp_channel(RDMAContext *rdma) > { > + struct rdma_cm_event *cm_event; > + int ret = -1; > + > /* > * Coroutine doesn't start until migration_fd_process_incoming() > * so don't yield unless we know we're running inside of a coroutine. > @@ -1505,13 +1508,37 @@ static int qemu_rdma_wait_comp_channel(RDMAContext *rdma) > * without hanging forever. > */ > while (!rdma->error_state && !rdma->received_error) { > - GPollFD pfds[1]; > + GPollFD pfds[2]; > pfds[0].fd = rdma->comp_channel->fd; > pfds[0].events = G_IO_IN | G_IO_HUP | G_IO_ERR; > + pfds[0].revents = 0; > + > + pfds[1].fd = rdma->channel->fd; > + pfds[1].events = G_IO_IN | G_IO_HUP | G_IO_ERR; > + pfds[1].revents = 0; > + > /* 0.1s timeout, should be fine for a 'cancel' */ > - switch (qemu_poll_ns(pfds, 1, 100 * 1000 * 1000)) { > + switch (qemu_poll_ns(pfds, 2, 100 * 1000 * 1000)) { > + case 2: > case 1: /* fd active */ > - return 0; > + if (pfds[0].revents) { > + return 0; > + } > + > + if (pfds[1].revents) { > + ret = rdma_get_cm_event(rdma->channel, &cm_event); > + if (!ret) { > + rdma_ack_cm_event(cm_event); > + } > + > + error_report("receive cm event while wait comp channel," > + "cm event is %d", cm_event->event); > + if (cm_event->event == RDMA_CM_EVENT_DISCONNECTED || > + cm_event->event == RDMA_CM_EVENT_DEVICE_REMOVAL) { > + return -EPIPE; > + } > + } > + break; > > case 0: /* Timeout, go around again */ > break; > -- > 1.8.3.1 > -- Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK