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


Re: [Xen-devel] shadow_fault()

To: hyj <hyjshanghai@xxxxxxxxxxx>
Subject: Re: [Xen-devel] shadow_fault()
From: Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Date: Mon, 25 Feb 2008 11:04:21 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 25 Feb 2008 03:05:29 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <000701c87785$36394de0$a2abe9a0$@com>
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: <000701c87785$36394de0$a2abe9a0$@com>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.13 (2006-08-11)
At 16:05 +0800 on 25 Feb (1203955540), hyj wrote:
>          I studying how Xen deals with shadow page fault. The code of
> shadow_fault() and its calling functions is too complex. I would be grateful
> if you can give me some detailed documentation on Xen's shadow page fault
> handling mechanism.

Alas, it suffers from the usual open-source lack of documentation.
There's only the code, and the mailing list.


Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Principal Software Engineer, Citrix Systems (R&D) Ltd.
[Company #02300071, SL9 0DZ, UK.]

Xen-devel mailing list

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