From: Eric Blake <eblake@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Cc: "David Airlie" <airlied@redhat.com>,
"Marc-André Lureau" <mlureau@redhat.com>
Subject: Re: [Qemu-devel] RFC: running the user interface in a thread ...
Date: Mon, 18 Jan 2016 13:34:49 -0700 [thread overview]
Message-ID: <569D4C69.5070304@redhat.com> (raw)
In-Reply-To: <1453110880.23289.7.camel@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 777 bytes --]
On 01/18/2016 02:54 AM, Gerd Hoffmann wrote:
> Hi folks,
>
> I'm starting to investigate if and how we can move the user interface
> code into its own thread instead of running it in the iothread and
> therefore avoid blocking the guest in case some UI actions take a little
> longer.
That, and so the UI can use localization without corrupting other
threads that MUST use the C locale (QMP parsing/output of floating point
is particularly important to get right with '.' instead of ',' for a
decimal separator).
>
> Suggestions how to tackle that?
Sadly, I don't have good suggestions here, as I've never done much in
the way of UI coding.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2016-01-18 20:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 9:54 [Qemu-devel] RFC: running the user interface in a thread Gerd Hoffmann
2016-01-18 20:34 ` Eric Blake [this message]
2016-01-19 13:01 ` Gerd Hoffmann
2016-01-19 13:38 ` Dr. David Alan Gilbert
2016-01-19 14:14 ` Gerd Hoffmann
2016-01-20 14:33 ` Kevin Wolf
2016-01-19 15:19 ` Markus Armbruster
2016-01-19 15:28 ` Daniel P. Berrange
2016-01-20 5:05 ` Eric Blake
2016-01-20 8:45 ` Gerd Hoffmann
2016-01-19 12:51 ` Kevin Wolf
2016-01-21 9:58 ` Stefan Hajnoczi
2016-01-21 10:39 ` Gerd Hoffmann
2016-01-21 10:52 ` Paolo Bonzini
2016-01-21 10:40 ` Daniel P. Berrange
2016-01-19 15:37 ` Daniel P. Berrange
2016-01-20 7:13 ` Gerd Hoffmann
2016-01-21 8:44 ` Dave Airlie
2016-01-21 9:05 ` Paolo Bonzini
2016-01-21 9:52 ` Gerd Hoffmann
2016-01-21 10:16 ` Paolo Bonzini
2016-01-22 1:38 ` Dave Airlie
2016-01-22 6:59 ` Gerd Hoffmann
2016-01-22 7:14 ` Dave Airlie
2016-01-21 9:00 ` Fam Zheng
2016-01-21 9:45 ` Gerd Hoffmann
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=569D4C69.5070304@redhat.com \
--to=eblake@redhat.com \
--cc=airlied@redhat.com \
--cc=kraxel@redhat.com \
--cc=mlureau@redhat.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).