From: Fabrice Bellard <fabrice@bellard.org>
To: jseward@acm.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Reducing X communication bandwidth
Date: Sat, 10 Jul 2004 15:53:10 +0200 [thread overview]
Message-ID: <40EFF4C6.7020305@bellard.org> (raw)
In-Reply-To: <200407100945.06998.jseward@acm.org>
Julian Seward wrote:
> [...]
> Anyway, QEMU from cvs is unusable like this, at least when
> running WinXP or Win2K. The SDL layer (qemu/sdl.c) blasts
> huge numbers of pixels across the network in response to even
> the simplest graphical operations. Notably, moving the mouse
> pointer is appalling, with an update rate of about twice per
> second, which is hopeless.
>
> The attached patch against sdl.c fixes this. It keeps a shadow
> copy of video memory. When a request arrives at sdl_update()
> to redraw an area, the area is compared against the shadow copy,
> and only the parts that have really changed are passed to
> SDL_UpdateRect(). The comparison is done at a granularity of
> 32x32 chunks of pixels.
> [...]
OK for the feature.
I just want to be sure it does not slow down the case where QEMU runs
locally (comparisons may be slower than just copying). So there should
be a specific support to detect if shared memory is used by SDL.
Another point is that it may not be necessary to add a second frame
buffer. By modifying the vga core a single line of memory should be
necessary to do the comparison.
Fabrice.
next prev parent reply other threads:[~2004-07-10 13:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-10 8:45 [Qemu-devel] Reducing X communication bandwidth Julian Seward
2004-07-10 9:10 ` Jan Dittmer
2004-07-11 10:15 ` Hetz Ben Hamo
2004-07-10 10:53 ` Jan Dittmer
2004-07-11 8:20 ` Jan Dittmer
2004-07-11 11:18 ` Julian Seward
2004-07-10 12:00 ` Brad Campbell
2004-07-10 12:42 ` Julian Seward
2004-07-10 13:53 ` Fabrice Bellard [this message]
2004-07-11 9:53 ` Johannes Schindelin
2004-07-11 11:22 ` Julian Seward
2004-07-12 10:16 ` Johannes Schindelin
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=40EFF4C6.7020305@bellard.org \
--to=fabrice@bellard.org \
--cc=jseward@acm.org \
--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).