From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MVger-0006Z1-VS for qemu-devel@nongnu.org; Tue, 28 Jul 2009 02:59:33 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MVgen-0006Yp-Mv for qemu-devel@nongnu.org; Tue, 28 Jul 2009 02:59:33 -0400 Received: from [199.232.76.173] (port=46137 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MVgen-0006Ym-J0 for qemu-devel@nongnu.org; Tue, 28 Jul 2009 02:59:29 -0400 Received: from mx20.gnu.org ([199.232.41.8]:21043) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MVgem-0002rZ-UD for qemu-devel@nongnu.org; Tue, 28 Jul 2009 02:59:29 -0400 Received: from mx2.redhat.com ([66.187.237.31]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MVgem-0002UH-0D for qemu-devel@nongnu.org; Tue, 28 Jul 2009 02:59:28 -0400 Message-ID: <4A6EA1CB.2030604@redhat.com> Date: Tue, 28 Jul 2009 09:59:23 +0300 From: Avi Kivity MIME-Version: 1.0 References: <1248468005-13907-1-git-send-email-glommer@redhat.com> <4A6AD034.4090802@web.de> <20090728010807.GR4776@poweredge.glommer> <4A6E9C7A.9080705@redhat.com> <4A6E9FCC.40909@web.de> In-Reply-To: <4A6E9FCC.40909@web.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [PATCH] RFC: use logging count for individual regions List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: Glauber Costa , qemu-devel@nongnu.org, aliguori@us.ibm.com On 07/28/2009 09:50 AM, Jan Kiszka wrote: > > >> Unlike the qemu dirty byte-map, the kvm dirty log can only service one >> user. As we have multiple users (vga and migration), we need some way >> to fix this impedance mismatch. I think refcounts are the easiest. >> > > This case is already handled upstream. If we had more users, we would > need refcounts. > If we turn off logging on migration failure, then we'd introduce a bug in vga logging, no? -- Do not meddle in the internals of kernels, for they are subtle and quick to panic.