From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:38482) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QZiUH-0003PY-32 for qemu-devel@nongnu.org; Thu, 23 Jun 2011 07:54:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QZiUF-00008r-Dc for qemu-devel@nongnu.org; Thu, 23 Jun 2011 07:54:20 -0400 Received: from mx1.redhat.com ([209.132.183.28]:48500) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QZiUE-00008Q-QS for qemu-devel@nongnu.org; Thu, 23 Jun 2011 07:54:19 -0400 Message-ID: <4E032961.8030607@redhat.com> Date: Thu, 23 Jun 2011 14:54:09 +0300 From: Avi Kivity MIME-Version: 1.0 References: <4E031F69.30407@redhat.com> <4E032605.9050009@web.de> <4E03271D.4040806@redhat.com> <4E0328F6.5020801@web.de> In-Reply-To: <4E0328F6.5020801@web.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 00/13] vga: dirty log cleanup, more linear mapping List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: Anthony PERARD , Anthony Liguori , Gerd Hoffmann , qemu-devel , "Michael S. Tsirkin" On 06/23/2011 02:52 PM, Jan Kiszka wrote: > On 2011-06-23 13:44, Avi Kivity wrote: > > On 06/23/2011 02:39 PM, Jan Kiszka wrote: > >> On 2011-06-23 13:11, Avi Kivity wrote: > >> > On 06/14/2011 07:53 PM, Jan Kiszka wrote: > >> >> A few optimizations and cleanups I came across when trying to > >> speed up > >> >> slow graphical grub unter non-cirrus vga. This series > >> >> - eliminates log_start/stop CPUPhysMemoryClient callbacks > >> >> - accelerates chain 4 vga mode under KVM > >> >> - fixes reset of vmware-vga > >> >> - cleans up vmware-vga a bit > >> >> > >> >> At least patch 8 is a candiate for 0.15 and stable. > >> > > >> > Yikes, most is all going away with the memory API (except the extra > >> > acceleration). > >> > >> Can't follow yet. What goes away? > > > > All the games with starting and stopping the log. > > That's what this series does as well (among other things). > > That the new API will look different for the devices is clear, also that > it may differ on the listener side. But if your API will not need any > kind of explicit start/stop callbacks for memory clients, then we are > moving in the right direction. Yes, looking at them, they certainly match what I'm doing. Will be fun rebasing over them. > > Now you start the log > > on the vram memory region and all the aliases, maps/unmaps, and mode > > changes are handled automatically. > > > > But I didn't get the patches yet, so no idea how much overlap. > > The patches were already sent last week, see [1] for the full history. > > Jan > > [1] http://thread.gmane.org/gmane.comp.emulators.qemu/106150 > Yeah, I missed them, even though you copied me. -- error compiling committee.c: too many arguments to function