From: Anthony Liguori <anthony@codemonkey.ws>
To: Nathan Baum <nathan@parenthephobia.org.uk>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC][PATCH] File-backed memory maps
Date: Fri, 18 Sep 2009 10:15:49 -0500 [thread overview]
Message-ID: <4AB3A425.3060305@codemonkey.ws> (raw)
In-Reply-To: <1253275896.11717.239.camel@localhost.localdomain>
Nathan Baum wrote:
> I'm mainly interested in the idea of moving the VNC server into its own
> process. It would listen for connections as usual and then send
> framebuffer updates from the file. Doing that also requires a
> side-channel for communicating graphics mode updates and peripheral
> input between QEMU and the VNC server. (Something like "-mouse
> <char-dev-spec> -keyboard <char-dev-spec>", perhaps?)
>
I think the preferred way to do this would be to introduce a shared
memory encoding to VNC. You could then implement or whatever as a VNC
client that used this shared memory transport.
You can't always share VGA remote because sometimes it's in planar
mode. However, in the cases where memory is proper ram, you could
potentially share that memory directly resulting in zero copies.
I think the ideal thing to do would be to share a file descriptor that
was mmap()'able. Sharing sys v IPC keys is also a possibility and would
better integrate with XShmImage.
Regards,
Anthony Liguori
prev parent reply other threads:[~2009-09-18 15:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 12:11 [Qemu-devel] [RFC][PATCH] File-backed memory maps Nathan Baum
2009-09-18 13:59 ` Jamie Lokier
2009-09-18 15:05 ` Nathan Baum
2009-09-18 16:10 ` Jamie Lokier
2009-09-18 15:15 ` Anthony Liguori [this message]
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=4AB3A425.3060305@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=nathan@parenthephobia.org.uk \
--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).