From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:33497) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QWWmO-0000Q8-B3 for qemu-devel@nongnu.org; Tue, 14 Jun 2011 12:47:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QWWmM-0004B8-UD for qemu-devel@nongnu.org; Tue, 14 Jun 2011 12:47:51 -0400 Received: from mx1.redhat.com ([209.132.183.28]:50086) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QWWmM-0004Aw-BU for qemu-devel@nongnu.org; Tue, 14 Jun 2011 12:47:50 -0400 Message-ID: <4DF790A9.4020408@redhat.com> Date: Tue, 14 Jun 2011 19:47:37 +0300 From: Avi Kivity MIME-Version: 1.0 References: <1307116614-11775-1-git-send-email-stefano.stabellini@eu.citrix.com> <4DF7403E.6000503@siemens.com> In-Reply-To: <4DF7403E.6000503@siemens.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [Xen-devel] Re: [PATCH] xen: avoid tracking the region 0xa0000 - 0xbffff List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: xen-devel@lists.xensource.com, "" , Alexander Graf , qemu-devel@nongnu.org, anthony.perard@citrix.com On 06/14/2011 02:04 PM, Jan Kiszka wrote: > BTW, if Xen is not able to track more than one dirty region, I think > it's time to fix that limitation. At some point it may no longer be > possible to work around it (who knows how the new memory API will look > like in this regard). > Since the memory API eventually passes its decisions to the accelerator (tcg/kvm/xen) it shouldn't be a problem to make the decision there as to which region actually gets logged. -- error compiling committee.c: too many arguments to function