From: Fam Zheng <famz@redhat.com>
To: Liviu Ionescu <ilg@livius.net>
Cc: QEMU Developer <Qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] experience with SDL2, event loop & main thread
Date: Mon, 12 Dec 2016 18:36:16 +0800 [thread overview]
Message-ID: <20161212103616.GB7918@lemon> (raw)
In-Reply-To: <151F368B-80DA-4DF6-837C-E2E0737E4AE6@livius.net>
On Mon, 12/12 12:20, Liviu Ionescu wrote:
>
> > On 12 Dec 2016, at 11:39, Fam Zheng <famz@redhat.com> wrote:
> >
> > ... I myself know next to nothing about SDL project.
>
> ok, neither do I.
>
>
> do you have any comments on the current situation of the SDL integration in
> QEMU? any comments on the conclusions I reached after integrating SDL2 into
> GNU ARM Eclipse QEMU?
>
> personally I do not like at all polling the SDL loop every 10 ms on a timer,
> but I currently have no other solution. I tried to move the I/O loop on a
> separate thread, but the Windows implementation of `poll` works only on the
> main thread.
Like I said ealier, instead of "polling" SDL events in a timer, how about
registering an EventNotifier in the main thread which is notified by the vCPU
thread upon a new graphics operation? That will fix the latency issue.
Fam
next prev parent reply other threads:[~2016-12-12 10:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-10 16:16 [Qemu-devel] experience with SDL2, event loop & main thread Liviu Ionescu
2016-12-12 3:35 ` Fam Zheng
2016-12-12 7:18 ` Liviu Ionescu
2016-12-12 7:39 ` Fam Zheng
2016-12-12 7:43 ` Liviu Ionescu
2016-12-12 9:39 ` Fam Zheng
2016-12-12 10:20 ` Liviu Ionescu
2016-12-12 10:36 ` Fam Zheng [this message]
2016-12-12 10:42 ` Daniel P. Berrange
2016-12-12 11:27 ` Liviu Ionescu
2016-12-12 12:28 ` Fam Zheng
2016-12-12 13:22 ` Liviu Ionescu
2016-12-12 14:51 ` Fam Zheng
2016-12-12 15:07 ` Liviu Ionescu
2016-12-13 7:04 ` Fam Zheng
2016-12-13 7:21 ` Liviu Ionescu
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=20161212103616.GB7918@lemon \
--to=famz@redhat.com \
--cc=Qemu-devel@nongnu.org \
--cc=ilg@livius.net \
/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).