WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] Prototype to use QEMU for PV guest framebuffer

To: "Daniel P. Berrange" <berrange@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] Prototype to use QEMU for PV guest framebuffer
From: "Ian Pratt" <Ian.Pratt@xxxxxxxxxxxx>
Date: Sun, 29 Jul 2007 23:03:09 +0100
Delivery-date: Sun, 29 Jul 2007 15:01:33 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20070727202844.GA8236@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcfQjOREwtGOKuV2RTCzdZSjQhWdjgBnw80g
Thread-topic: [Xen-devel] Prototype to use QEMU for PV guest framebuffer
> Pushing mouse & keyboard events through from QEMU to PVFB frontend is
> trivial. The only bit I'm unhappy about is that QEMU can't access the
> guest framebuffer directly. The DisplayState * struct has its own copy
> of the framebuffer - allocated by the VNC or SDL impls in QEMU - and
> so whenever the guest framebuffer changes, we have to memcpy() the
data
> from the guest into the QEMU framebuffer. Still, this is no worse than
> what the HVM guests already do. Its probably not too hard to change
the
> QEMU impl of VNC / SDL to use the guest framebuffer directly if we did
> a little re-factoring. I wanted to keep it simple for now & not change
> any of the upstream QEMU code.
> 
> This attached patch is against the current upstream QEMU  CVS code,
not
> Xen's ioemu, since I wanted to work against pristine QEMU codebase &
avoid
> any potential wierd iteractions with HVM stuff added to ioemu. The
diff is

It'll certainly be good to see the back of libvncserver.

Could you investigate whether this patch applies to qemu-dm easily
enough?

Thanks,
Ian




_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>