From: Blue Swirl <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [6391] Fix nographic mode and VNC
Date: Wed, 21 Jan 2009 22:44:17 +0200 [thread overview]
Message-ID: <f43fc5580901211244t6168057ci7c5cddcd9bc380e9@mail.gmail.com> (raw)
In-Reply-To: <20090121202904.GE5237@const.famille.thibault.fr>
On 1/21/09, Samuel Thibault <samuel.thibault@ens-lyon.org> wrote:
> Blue Swirl, le Wed 21 Jan 2009 22:16:15 +0200, a écrit :
>
> > On 1/21/09, Samuel Thibault <samuel.thibault@ens-lyon.org> wrote:
> > > Blue Swirl, le Wed 21 Jan 2009 19:28:14 +0000, a écrit :
> > >
> > > > +static void nographic_update(void *opaque)
> > > > +{
> > > > + uint64_t interval = GUI_REFRESH_INTERVAL;
> > > > +
> > > > + qemu_mod_timer(nographic_timer, interval + qemu_get_clock(rt_clock));
> > > > +}
> > >
> > >
> > > Maybe less often than 33 times per second? SDL uses 2 times per second
> > > when the window is minimized.
> >
> > I just tried: it's not enough, the serial console is unusably slow.
>
>
> Mmm, I haven't followed everything so I probably misunderstand, but I
> guess you are talking about a serial console on stdio, shouldn't we
> already be monitoring the stdin fd to break the cpu emulation loop?
Some other way, like SIGIO or IO worker thread, may work too. It may
also be a big change.
> It'd be a shame to have to poll every 30ms all the time because of the
> cpu emulation loop, even when we can just select in main_loop_wait
> because the cpu is idle.
OpenBIOS reads the console in a busy loop, the CPU will never be idle.
Maybe the timer period could be scaled automatically: if for X periods
there has been no activity on the select() file descriptors, increase
the period by factor Y. Also if for X periods there has always been
activity, decrease the period.
next prev parent reply other threads:[~2009-01-21 20:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 19:28 [Qemu-devel] [6391] Fix nographic mode and VNC Blue Swirl
2009-01-21 19:39 ` Stefano Stabellini
2009-01-21 19:52 ` Blue Swirl
2009-01-21 19:56 ` Stefano Stabellini
2009-01-21 20:03 ` Samuel Thibault
2009-01-21 20:16 ` Blue Swirl
2009-01-21 20:29 ` Samuel Thibault
2009-01-21 20:44 ` Blue Swirl [this message]
2009-01-21 21:33 ` Anthony Liguori
2009-01-22 0:04 ` Paul Brook
2009-01-22 3:31 ` Anthony Liguori
2009-01-22 4:23 ` Paul Brook
2009-01-22 12:36 ` Ian Jackson
2009-01-23 18:59 ` Paul Brook
2009-01-22 15:29 ` Anthony Liguori
2009-01-23 18:20 ` Paul Brook
2009-01-23 19:37 ` Anthony Liguori
2009-01-25 19:57 ` Jamie Lokier
2009-01-25 23:25 ` Paul Brook
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=f43fc5580901211244t6168057ci7c5cddcd9bc380e9@mail.gmail.com \
--to=blauwirbel@gmail.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).