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

[Xen-devel] Re: [PATCH][HVM] remove qemu shadow_vram patch for performan

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Re: [PATCH][HVM] remove qemu shadow_vram patch for performance
From: Anthony Liguori <anthony@xxxxxxxxxxxxx>
Date: Wed, 21 Mar 2007 16:09:11 -0500
Delivery-date: Wed, 21 Mar 2007 14:08:29 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C21ED565.B88C%keir@xxxxxxxxxxxxx>
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: <20070315033005.GD12238@xxxxxxxxxxxxxxxxxxxxxx> <C21ED565.B88C%keir@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.10 (X11/20070306)
Keir Fraser wrote:


On 15/3/07 03:30, "Zhai, Edwin" <edwin.zhai@xxxxxxxxx> wrote:

remove qemu shadow_vram patch and force a whole screen update each time for
performance.

W/O this patch, there is huge performance drop in HVM domain when adding other
guest(windows or linux with xwindow).

shadow_vram_revert.patch - revert the shadow_vram patch
shadow_vram_force_update.patch - explictly redraw screen each time

How can updating the whole screen 30 times a second be faster than the
memcmp() that we do currently?

It really depends. The VNC display already has a minimization mechanism so doign the memcmp() in the vga driver doesn't help at all.

For SDL, when using X, it's going to be doing an XShmImage so the difference is only in the size of update (no data is transferred to the X server). If the X server is double buffering the framebuffer (which I have to assume it's doing), then you're just paying the cost of a memcpy() in the X server that you would normally pay in qemu-dm.

However, if you're forwarding SDL over X, or for some reason your X server isn't using XShmImage, this patch will slow things down considerably.

Perhaps this should be made a configuration option?

Regards,

Anthony Liguori

 -- Keir


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