From: "Daniel P. Berrange" <berrange@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: Liviu Ionescu <ilg@livius.net>, QEMU Developer <Qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] experience with SDL2, event loop & main thread
Date: Mon, 12 Dec 2016 10:42:28 +0000 [thread overview]
Message-ID: <20161212104228.GA3597@redhat.com> (raw)
In-Reply-To: <20161212103616.GB7918@lemon>
On Mon, Dec 12, 2016 at 06:36:16PM +0800, Fam Zheng wrote:
> 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.
Also, note that SDL is not the only backend that requires all graphics
operations to take place in a single thread. GTK2/3 both require that
everything is done in the same thread. So if there's any parts of QEMU
that are triggering graphics operations in non-main threads, we really
need to make sure any fix applies to all QEMU graphics backends, not
just SDL2.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://entangle-photo.org -o- http://search.cpan.org/~danberr/ :|
next prev parent reply other threads:[~2016-12-12 10:42 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
2016-12-12 10:42 ` Daniel P. Berrange [this message]
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=20161212104228.GA3597@redhat.com \
--to=berrange@redhat.com \
--cc=Qemu-devel@nongnu.org \
--cc=famz@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.