qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [patch] cocoa.m - Core Graphics support
Date: Wed, 30 Jan 2008 15:54:50 -0600	[thread overview]
Message-ID: <47A0F22A.9040704@codemonkey.ws> (raw)
In-Reply-To: <40275543-3906-421D-B6DB-13B1BA72E35B@kberg.ch>

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

  parent reply	other threads:[~2008-01-30 21:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-21 16:18 [Qemu-devel] [patch] cocoa.m - Core Graphics support Mike Kronenberg
2008-01-30 18:59 ` Alexander Graf
2008-01-30 19:05   ` Alexander Graf
2008-01-30 20:30   ` Mike Kronenberg
2008-01-30 20:39     ` Johannes Schindelin
2008-01-30 21:18       ` andrzej zaborowski
2008-01-31  9:15         ` Jamie Lokier
2008-01-30 21:00     ` Pierre d'Herbemont
2008-01-30 21:54     ` Anthony Liguori [this message]
2008-01-31  9:46       ` Jamie Lokier
2008-01-31 11:38         ` Julian Seward
2008-01-31 22:40         ` Anthony Liguori
2008-01-31 23:03           ` Jamie Lokier
2008-01-31  8:29     ` Alexander Graf
2008-01-30 20:44   ` Mike Kronenberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47A0F22A.9040704@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).