From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MofBm-0006yz-U6
	for qemu-devel@nongnu.org; Fri, 18 Sep 2009 11:15:59 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MofBi-0006vD-52
	for qemu-devel@nongnu.org; Fri, 18 Sep 2009 11:15:58 -0400
Received: from [199.232.76.173] (port=58467 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MofBi-0006v7-1m
	for qemu-devel@nongnu.org; Fri, 18 Sep 2009 11:15:54 -0400
Received: from qw-out-1920.google.com ([74.125.92.149]:37093)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1MofBh-00028A-Q5
	for qemu-devel@nongnu.org; Fri, 18 Sep 2009 11:15:53 -0400
Received: by qw-out-1920.google.com with SMTP id 5so325070qwc.4
	for <qemu-devel@nongnu.org>; Fri, 18 Sep 2009 08:15:53 -0700 (PDT)
Message-ID: <4AB3A425.3060305@codemonkey.ws>
Date: Fri, 18 Sep 2009 10:15:49 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [RFC][PATCH] File-backed memory maps
References: <1253275896.11717.239.camel@localhost.localdomain>
In-Reply-To: <1253275896.11717.239.camel@localhost.localdomain>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Nathan Baum <nathan@parenthephobia.org.uk>
Cc: qemu-devel@nongnu.org

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