From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JKKti-0002So-CO for qemu-devel@nongnu.org; Wed, 30 Jan 2008 16:55:10 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JKKtg-0002Qf-0p for qemu-devel@nongnu.org; Wed, 30 Jan 2008 16:55:10 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JKKtf-0002Qc-Sd for qemu-devel@nongnu.org; Wed, 30 Jan 2008 16:55:07 -0500 Received: from el-out-1112.google.com ([209.85.162.181]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JKKtf-0006Y7-Dw for qemu-devel@nongnu.org; Wed, 30 Jan 2008 16:55:07 -0500 Received: by el-out-1112.google.com with SMTP id y26so186817ele.18 for ; Wed, 30 Jan 2008 13:54:56 -0800 (PST) Message-ID: <47A0F22A.9040704@codemonkey.ws> Date: Wed, 30 Jan 2008 15:54:50 -0600 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] [patch] cocoa.m - Core Graphics support References: <13FD6BC9-36B9-4911-82D4-739AC5E10E66@kberg.ch> <4E3770A5-4564-49DF-B868-511F5935F7CD@csgraf.de> <40275543-3906-421D-B6DB-13B1BA72E35B@kberg.ch> In-Reply-To: <40275543-3906-421D-B6DB-13B1BA72E35B@kberg.ch> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Mike Kronenberg wrote: > While testing with Quartzdebug, I realized, that qemu is updating > always the whole screenwidth even if only the mouse is moved... is > this a qemu problem, or is this the default windows behaviour? VGA framebuffer operations come in as memory operations. They're tracked by watching what memory gets dirtied. This can only operate at a page-granularity so this results in scan-line granularity updates. The VNC front-end goes to great lengths to keep a shadowed framebuffer and reduce these updates to a smaller update region. You could possibly look at refactoring that code. However... I would be amazed if screen updates on OS X are so slow that it would make a difference if updates are in scanline granularities. The copying latency is nothing compared to the other latencies in QEMU. A modern processor can move memory at an extremely high speed. At a refresh rate of 30 times per second, this is only ~4MB of data for mouse movements. A typical processor can easily handle many GB of data per second. Regards, Anthony Liguori > Mike > > [1] > http://developer.apple.com/documentation/Carbon/Conceptual/QuickDrawToQuartz2D/tq_image_data/chapter_6_section_2.html#//apple_ref/doc/uid/TP40001098-CH227-BBCFFDBB