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/
Home Products Support Community News


[Xen-devel] [PATCH] VGA acceleration utilizing shadow logdirty functiona

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] [PATCH] VGA acceleration utilizing shadow logdirty functionality
From: "Huang, Xinmei" <xinmei.huang@xxxxxxxxx>
Date: Thu, 17 May 2007 17:53:52 +0800
Delivery-date: Thu, 17 May 2007 02:53:22 -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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AceYZSldSoX4x3tKTEyhYB9cAR9S5AAA7FKw
Thread-topic: [PATCH] VGA acceleration utilizing shadow logdirty functionality
Hi all, 

here's a patch for vga acceleration. Can anyone give some suggestions ?

Shadow log dirty mode is enabled to track vram pages dirty status.When
drawing guest graphic screen, VGA dm gets the dirty bitmap of mmio space
through one shadow control hypercall. VGA
dm updates dirty pages of vram according to the dirty bitmap.Hypervisor
marks the vram pages read-only for the guest, in order to log the write
access to these pages from the guest. Once a vram page is written and
logged by hypervisor, it becomes r/w for this guest. After returning the
dirty bitmap to VGA dm, hypervisor re-marks these vram pages read-only
for next round.

This patch would save the heavy overhead of current vram dirty
algorithm(compare between vram and vram copy of last round), albeit
brings overhead of ram page fault for dirty status log. 

Any suggesion will be really appreciated.

Thanks !

Attachment: vga.logdirty.patch
Description: vga.logdirty.patch

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>