From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [RFC v4 00/58] Memory API Date: Wed, 20 Jul 2011 19:52:22 +0300 Message-ID: <4E2707C6.7060603@redhat.com> References: <4E25B85C.1030809@siemens.com> <4E25BB7A.7030105@redhat.com> <4E25BF26.6080900@siemens.com> <4E268E20.5050807@redhat.com> <4E26BF77.7070705@siemens.com> <4E26C290.8010604@redhat.com> <4E26DECC.9000700@siemens.com> <4E26E716.2090109@redhat.com> <20110720143720.GC6787@redhat.com> <4E26EC22.1030309@redhat.com> <20110720161018.GB8077@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Jan Kiszka , "qemu-devel@nongnu.org" , "kvm@vger.kernel.org" To: "Michael S. Tsirkin" Return-path: Received: from mx1.redhat.com ([209.132.183.28]:31326 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752749Ab1GTQw3 (ORCPT ); Wed, 20 Jul 2011 12:52:29 -0400 In-Reply-To: <20110720161018.GB8077@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 07/20/2011 07:10 PM, Michael S. Tsirkin wrote: > > and vga could do it if the vnc display > > is disconnected, or if the update rate is so high it can just assume > > all memory is dirty. > > Yes, but it's not something *devices* should be doing. No one knows about the frame buffer except the vga device. > > >What devices seem to need, instead, is enable/disable a region > > >through a back channel. > > > > What do you mean? > > At least for qxl, all it seems to do is enable/disable > logging when the region is enabled disabled. > I'm not sure I follow what does vmware do - something > similar only with a custom register instead of > the standard memory enable? pv vga like vmware and qxl disables logging when the pv interface is active. -- error compiling committee.c: too many arguments to function