From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Paul Brook <paul@codesourcery.com>, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Extremely slow graphic updates
Date: Tue, 20 Jan 2009 17:21:32 +0000 [thread overview]
Message-ID: <4976081C.2090407@eu.citrix.com> (raw)
In-Reply-To: <20090120165534.GY29175@csclub.uwaterloo.ca>
Lennart Sorensen wrote:
> I was trying to come up with a simple test case to show the problem,
> but found another one. If I simply run qemu-system-ppc -vnc :1 I get
> nothing on VNC. Using -sdl I get the openbios prompt. If I use both
> -vnc :1 and -sdl I get openbios showing on both. vnc by itself seems to
> only start displaying something once something other than openbios is
> running, like the bootloader or linux kernel. That doesn't seem right.
I could reproduce this issue.
The problem seems to be strictly related to the gui_timer:
Currently we set the gui_timer only if someone implements dpy_refresh.
Since sdl implements dpy_refresh while vnc does not, when only vnc is
enabled the gui_timer is never allocated.
The weird thing is that even if I change the gui_update function to be
something like:
static void gui_update(void *opaque)
{
uint64_t interval = GUI_REFRESH_INTERVAL;
DisplayState *ds = opaque;
DisplayChangeListener *dcl = ds->listeners;
qemu_mod_timer(ds->gui_timer, interval + qemu_get_clock(rt_clock));
}
Vnc still works correctly.
So it doesn't matter the actual implementation of the function to be
called, as long as it is called.
next prev parent reply other threads:[~2009-01-20 17:25 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
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 [this message]
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=4976081C.2090407@eu.citrix.com \
--to=stefano.stabellini@eu.citrix.com \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=paul@codesourcery.com \
--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).