From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55658) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YxER0-0003xB-BT for qemu-devel@nongnu.org; Tue, 26 May 2015 08:58:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YxEQx-0006jQ-35 for qemu-devel@nongnu.org; Tue, 26 May 2015 08:58:18 -0400 Received: from mx1.redhat.com ([209.132.183.28]:47671) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YxEQw-0006jM-V1 for qemu-devel@nongnu.org; Tue, 26 May 2015 08:58:15 -0400 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (Postfix) with ESMTPS id 87A538E51E for ; Tue, 26 May 2015 12:58:14 +0000 (UTC) Date: Tue, 26 May 2015 20:58:11 +0800 From: Fam Zheng Message-ID: <20150526125811.GD21680@ad.nay.redhat.com> References: <1430152117-100558-1-git-send-email-pbonzini@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1430152117-100558-1-git-send-email-pbonzini@redhat.com> Subject: Re: [Qemu-devel] [PATCH v2 00/29] Dirty bitmap atomic access and optimizations List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: qemu-devel@nongnu.org, stefanha@redhat.com, mst@redhat.com On Mon, 04/27 18:28, Paolo Bonzini wrote: > Patches 1-4 are cleanups to DIRTY_MEMORY_VGA users. > > Patches 5-12 are the first cleanup (KVM treats migration as just > another client). Patches 13-14 are a simple optimization that is enabled > by these patches. > > Patches 15-18 are bonus cleanups to translate-all.c's dirty memory > tracking for TCG. > > Patches 19-22 are the second cleanup (avoid modifications to unused > dirty bitmaps). > > Patches 23-28 are Stefan's patches for atomic access to the dirty > bitmap, which has no performance impact in the common case thanks to > the previous work. > > Patch 29 is an unrelated strengthening of assertions, that mst spotted > while reviewing v1. I've looked at everything except patch 18, which is really beyond my understanding. Since it's running late for me now, I'll probably try patch 3 again tomorrow. Thanks, Fam