From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:39042) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bnVvF-00077Z-V7 for qemu-devel@nongnu.org; Fri, 23 Sep 2016 15:14:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bnVvC-0006hp-Pl for qemu-devel@nongnu.org; Fri, 23 Sep 2016 15:14:09 -0400 Received: from mx1.redhat.com ([209.132.183.28]:51572) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bnVvC-0006hZ-JI for qemu-devel@nongnu.org; Fri, 23 Sep 2016 15:14:06 -0400 From: "Dr. David Alan Gilbert (git)" Date: Fri, 23 Sep 2016 20:14:01 +0100 Message-Id: <1474658044-9479-1-git-send-email-dgilbert@redhat.com> Subject: [Qemu-devel] [PATCH 0/3] RDMA error handling List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org, amit.shah@redhat.com, quintela@redhat.com, michael@hinespot.com From: "Dr. David Alan Gilbert" lp: https://bugs.launchpad.net/qemu/+bug/1545052 The RDMA code tends to hang if the destination dies in the wrong place; this series doesn't completely fix that, but in cases where the destination knows there's been an error, it makes sure it tells the source and that cleans up quickly. If the destination just dies, then the source still hangs and I still need to look at better ways to fix that. Dave Dr. David Alan Gilbert (3): migration/rdma: Pass qemu_file errors across link migration: Make failed migration load set file error migration/rdma: Don't flag an error when we've been told about one migration/rdma.c | 9 ++++++++- migration/savevm.c | 19 ++++++++++++------- 2 files changed, 20 insertions(+), 8 deletions(-) -- 2.7.4