All of lore.kernel.org
 help / color / mirror / Atom feed
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 15:39:15 +0800	[thread overview]
Message-ID: <20161212073915.GC3725@lemon> (raw)
In-Reply-To: <908F0328-771A-4269-8301-9A7D08BD585F@livius.net>

On Mon, 12/12 09:18, Liviu Ionescu wrote:
> 
> > On 12 Dec 2016, at 05:35, Fam Zheng <famz@redhat.com> wrote:
> > 
> > Isn't it possible to notify the main thread with an EventNotifier and process
> > the deferred events in its handler?
> 
> ideally, the SDL main loop might be re-implemented asynchronously, for example
> using a pipe to pass the events, and in this case the SDL would be just a
> regular client of the main I/O loop.
> 
> any idea how difficult would be to push any changes to SDL?

Not sure I understand this question, could you be more specific?

Fam

  reply	other threads:[~2016-12-12  7:39 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 [this message]
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
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=20161212073915.GC3725@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 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.