Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751143AbdCPBkf (ORCPT ); Wed, 15 Mar 2017 21:40:35 -0400 Received: from mga02.intel.com ([134.134.136.20]:43210 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750846AbdCPBkc (ORCPT ); Wed, 15 Mar 2017 21:40:32 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.36,170,1486454400"; d="scan'208";a="76688385" Subject: Re: [Qemu-devel] kvm bug in __rmap_clear_dirty during live migration To: Paolo Bonzini , fangying , "Herongguang (Stephen)" , Chris Friesen , "Han, Huaitong" , "hangaohuai@huawei.com" , stable@vger.kernel.org References: <589C7E96.9060905@huawei.com> <589D83CE.1090803@huawei.com> <589DDC05.9010807@windriver.com> <58AA51D6.6020508@huawei.com> <1487565495.3740.27.camel@intel.com> <58AD0094.90304@windriver.com> <4dd92012-626a-2d80-9adb-0be398f73eb1@redhat.com> <58AD92AE.6040502@windriver.com> <6c5567f4-192d-aefd-90e4-89f53479c24e@redhat.com> <58AF9921.6060201@huawei.com> <58B04CD3.7010304@windriver.com> <7fdf2551-3d55-1bd9-2848-720a880cc93e@redhat.com> <58B0E191.6040108@huawei.com> <50916996-297e-a794-38e8-5c7ca9389419@linux.intel.com> Cc: "kvm@vger.kernel.org" , "xudong.hao@linux.intel.com" , "qemu-devel@nongnu.org" , "wangxinxin.wang@huawei.com" , "rkrcmar@redhat.com" , "guangrong.xiao@linux.intel.com" , linux-kernel@vger.kernel.org From: "Huang, Kai" Message-ID: <84e697fb-0309-faa9-9f10-90235f839db6@linux.intel.com> Date: Thu, 16 Mar 2017 14:40:20 +1300 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 301 Lines: 18 Thanks! Thanks, -Kai On 3/14/2017 5:57 AM, Paolo Bonzini wrote: > > > On 13/03/2017 15:58, fangying wrote: >> Hi, Huang Kai >> >> After weeks of intensive testing, we think the problem is solved and >> this issue can be closed. > > Thanks for the update. We got to the same conclusion. > > Paolo >