From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:47840) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bzGQC-0003wd-RV for qemu-devel@nongnu.org; Wed, 26 Oct 2016 01:06:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bzGQ8-0008Qh-Mz for qemu-devel@nongnu.org; Wed, 26 Oct 2016 01:06:40 -0400 Received: from mx1.redhat.com ([209.132.183.28]:46150) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1bzGQ8-0008QS-He for qemu-devel@nongnu.org; Wed, 26 Oct 2016 01:06:36 -0400 Date: Wed, 26 Oct 2016 10:36:31 +0530 From: Amit Shah Message-ID: <20161026050631.GE1679@amit-lp.rh> References: <1476792613-11712-1-git-send-email-zhang.zhanghailiang@huawei.com> <1476792613-11712-6-git-send-email-zhang.zhanghailiang@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1476792613-11712-6-git-send-email-zhang.zhanghailiang@huawei.com> Subject: Re: [Qemu-devel] [PATCH COLO-Frame (Base) v21 05/17] COLO: Establish a new communicating path for COLO List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: zhanghailiang Cc: quintela@redhat.com, qemu-devel@nongnu.org, dgilbert@redhat.com, wency@cn.fujitsu.com, lizhijian@cn.fujitsu.com, xiecl.fnst@cn.fujitsu.com On (Tue) 18 Oct 2016 [20:10:01], zhanghailiang wrote: > This new communication path will be used for returning messages > from Secondary side to Primary side. > > Signed-off-by: zhanghailiang > Signed-off-by: Li Zhijian > Reviewed-by: Dr. David Alan Gilbert Reviewed-by: Amit Shah > @@ -63,8 +75,24 @@ void *colo_process_incoming_thread(void *opaque) > migrate_set_state(&mis->state, MIGRATION_STATUS_ACTIVE, > MIGRATION_STATUS_COLO); > > + mis->to_src_file = qemu_file_get_return_path(mis->from_src_file); > + if (!mis->to_src_file) { > + error_report("COLO incoming thread: Open QEMUFile to_src_file failed"); > + goto out; > + } > + /* > + * Note: We set the fd to unblocked in migration incoming coroutine, > + * But here we are in the COLO incoming thread, so it is ok to set the > + * fd back to blocked. > + */ > + qemu_file_set_blocking(mis->from_src_file, true); Why does it need to be blocking? Amit