Re: [Xen-devel] Readonly memory for guest domain

To:	"Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject:	Re: [Xen-devel] Readonly memory for guest domain
From:	"Peter Teoh" <htmldeveloper@xxxxxxxxx>
Date:	Thu, 13 Sep 2007 09:59:59 +0800
Cc:	xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date:	Wed, 12 Sep 2007 19:00:22 -0700
Dkim-signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=ertQxNf6Syo7q3jiEE3xETKA1PBylqFIFGph5/c1Di0=; b=WHerkS7exyaboSLIMbkAr5c8sUL9wNcH0DPebILQhNvrza0EXrhzvRE3t9XwXKmk2/LNXSPDAx4BDcxb0mtM9OB969Mf0NVNKvtXNJfPfA2TdfNRmjvtaClW+P1BMUne5z4MHpa4DY+Ntg3c4enRsMYhUtZQCsRAkZZKUBm3jsM=
Domainkey-signature:	a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=UAzT5EU3jnRGBa8xN38IRgH7i0symz422dhtweukLkIH/zvi3zGiRuxDDote3cHL6lu0BdtQEPnJzChwKrmOeg4VDFCSRwNSuuSFniv5Rtv3OeKF2VI4jBD/7fAA32gF2RnY7OSLIML3AKJOyvWTd9kiSaxhL2ybBYRZEAgvGMA=
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxx
In-reply-to:	<C30D53BF.D73B%Keir.Fraser@xxxxxxxxxxxx>
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:	<00ca01c7f4db$69d991f0$9a010a0a@eeyore> <C30D53BF.D73B%Keir.Fraser@xxxxxxxxxxxx>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 9/12/07, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote:

Xen does not have this general read-only restriction. It does force page tables to be read-only, otherwise a guest could grant itself access to arbitrary memory that it does not own.

Thank you for the answer. In the first place, we will not know what is pagetable or non-pagetable memory. For example, during dom0/domU initialisation, the guest OS will query the e820 bios mechanism for physical memory availability, and the guest OS (paravirt or HVM) will then assign different parts of the physical memory for pagetable construction. Then after all the pagetable is completely constructed, the CR3 is loaded, which started the hardware MMU operation. So therefore, before the CR3 is loaded the entire physical memory is marked as readonly, and after the CR3 is loaded, only those memory not involved in pagetable mapping are unmarked readonly?

Does not seem right, as guest OS can change the CR3 anytime subsequently as well.

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

WARNING - OLD ARCHIVES

xen-devel

Re: [Xen-devel] Readonly memory for guest domain