From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: qemu-devel@nongnu.org
Cc: Paul Brook <paul@codesourcery.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [Qemu-devel] Re: Extremely slow graphic updates
Date: Tue, 20 Jan 2009 13:15:33 -0500 [thread overview]
Message-ID: <20090120181533.GZ29175@csclub.uwaterloo.ca> (raw)
In-Reply-To: <20090120170933.GF5177@const.bordeaux.inria.fr>
On Tue, Jan 20, 2009 at 06:09:33PM +0100, Samuel Thibault wrote:
> Ah, that rings me a bell. There was problem with that, something like
> now that sdl uses SDL_BlitSurface/SDL_Flip there is an X roundtrip,
> which is awfully slow over ssh. Would you be able to try without ssh?
That would be tricky since it is running on another machine. I will
try. I do believe someone else said that they could confirm the slow
behaviour with 6336 running locally as well. It may be that some X
drivers are slow at SDL_Flip and SDL_BlitSurface.
Hmm, my X server isn't compiled to allow tcp connections (only local
sockets), so avoiding ssh looks hard too.
Maybe Xvnc can do it. yeah Xvnc4 as an X server did the job, and I
vnc'd to it so qemu was running entirely locally on the machine with an
X connection. Works at normal speed.
So how does one fix this, since the change in 6336 makes it rather
painful for those where SDL_Flip and company are inefficient.
--
Len Sorensen
next prev parent reply other threads:[~2009-01-20 18:15 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-19 16:26 [Qemu-devel] qemu-system-ppc seems slow today Lennart Sorensen
2009-01-19 17:09 ` Aurelien Jarno
2009-01-19 17:49 ` Lennart Sorensen
2009-01-19 18:07 ` Lennart Sorensen
2009-01-19 18:39 ` Aurelien Jarno
2009-01-19 19:42 ` Lennart Sorensen
2009-01-20 0:53 ` Lennart Sorensen
2009-01-20 1:01 ` François Revol
2009-01-20 1:33 ` [Qemu-devel] Extremely slow graphic updates (was: qemu-system-ppc seems slow today) Paul Brook
2009-01-20 1:54 ` [Qemu-devel] Re: Extremely slow graphic updates Anthony Liguori
2009-01-20 11:22 ` Stefano Stabellini
2009-01-20 11:28 ` Stefano Stabellini
2009-01-20 14:46 ` Lennart Sorensen
2009-01-20 14:45 ` Lennart Sorensen
2009-01-20 15:21 ` Stefano Stabellini
2009-01-20 16:55 ` Lennart Sorensen
2009-01-20 17:09 ` Samuel Thibault
2009-01-20 18:15 ` Lennart Sorensen [this message]
2009-01-20 18:16 ` Stefano Stabellini
2009-01-20 18:25 ` Lennart Sorensen
2009-01-20 19:35 ` Lennart Sorensen
2009-01-20 19:46 ` Jamie Lokier
2009-01-20 20:02 ` Lennart Sorensen
2009-01-20 20:12 ` Jamie Lokier
2009-01-20 20:17 ` Lennart Sorensen
2009-01-20 19:38 ` Stefano Stabellini
2009-01-20 20:05 ` Lennart Sorensen
2009-01-20 20:30 ` Avi Kivity
2009-01-20 18:59 ` Samuel Thibault
2009-01-20 17:21 ` Stefano Stabellini
2009-01-20 17:35 ` Stefano Stabellini
2009-01-20 18:11 ` Paul Brook
2009-01-20 18:48 ` Re : " Sylvain Petreolle
2009-01-20 21:29 ` Stefan Weil
2009-01-21 1:50 ` Paul Brook
2009-01-21 15:23 ` Lennart Sorensen
2009-01-21 20:06 ` Stefano Stabellini
2009-01-21 21:29 ` Lennart Sorensen
2009-01-21 21:49 ` Lennart Sorensen
2009-01-21 21:52 ` Stefano Stabellini
2009-01-22 0:20 ` Paul Brook
2009-01-22 13:19 ` Lennart Sorensen
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=20090120181533.GZ29175@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
/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).