From: Kevin Wolf <kwolf@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "David Airlie" <airlied@redhat.com>,
"Marc-André Lureau" <mlureau@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] RFC: running the user interface in a thread ...
Date: Wed, 20 Jan 2016 15:33:14 +0100 [thread overview]
Message-ID: <20160120143314.GC4793@noname.redhat.com> (raw)
In-Reply-To: <1453212861.18326.97.camel@redhat.com>
Am 19.01.2016 um 15:14 hat Gerd Hoffmann geschrieben:
> Hi,
>
> > That does feel safer, if you can find an efficient way to do the graphics.
> > A lot less code running with the privs of the qemu process.
>
> That is where it starts to become tricky ...
>
> On modern linux we can simply use dma-bufs.
>
> On older linux and generic posix (*bsd etc) we should be able to use
> sysv shared memory.
>
> As MacOS X is based on BSD I'd expect sysv shared memory is available
> there too. Possibly we can use something more efficient there, we have
> macos-specific ui code anyway.
>
> Windows? Hmm, no idea how to shared memory there.
>
> We also need a control channel, to manage the shm bufs, to send user
> input (kbd/mouse), to implement some control things (machine menu in gtk
> ui). One option would be to simply use the monitor for that. The other
> one is to invent something limited to the stuff actually needed instead
> of handing over a dangerous swiss army knife to the process running the
> UI. Hmm, maybe a new monitor mode with a limited set of commands would
> do too.
I think you need to offer the full monitor command set anyway because
a UI that is on par with SDL or GTK must provide a monitor interface to
the user.
Kevin
next prev parent reply other threads:[~2016-01-20 14:33 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
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 [this message]
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=20160120143314.GC4793@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=airlied@redhat.com \
--cc=dgilbert@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 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.