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] Readonly memory for guest domain

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Readonly memory for guest domain
From: "Peter Teoh" <htmldeveloper@xxxxxxxxx>
Date: Wed, 12 Sep 2007 11:15:02 +0800
Delivery-date: Tue, 11 Sep 2007 20:15:41 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:from:to:subject:date:mime-version:content-type:x-priority:x-msmail-priority:x-mailer:x-mimeole; bh=zqp0lgRo4p1wsmgMXFckBqtBuuTXULpKaFQfzEh/MVk=; b=geUCyZvTX6H/vYfl9RkX04IdDBVFrBX6XENZetlvJtclU0aUpKqxMlnqj32carTxjWhYAvEy1iF2rq6qmSa6tofX9co1yZO8OMQJpauHMrvTZX98CYPULl7Q6VHo/XmbDfAVDvtB4UzrB59xulJ1qVYD0RmbpjzGJL5qFIcXIoQ=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:from:to:subject:date:mime-version:content-type:x-priority:x-msmail-priority:x-mailer:x-mimeole; b=RKriW0EwybBljsulhYf8jGrbqgh3GKGhrOLfdovBmOtkohZLHISP3oPKBdaGl1IRuf50Z0KuPJoYBokoSexxv4dCcs8dd/t0Qb46bB7lQdr+5fAdD0p2zq9wuKhf1ODQYIljUKhFy44lfhJm1Jr2U5/GK3copH7ED15XF6PX6wg=
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
Sorry, I think may have found the answer.   The real answer is because the guest should be hidden from the real physical PTE page table mapping.   And since all the guest page table are faked, a mechanism is needed to inform the hypervisor to remap to the real physical mapping.   The mechanism present used to do this is setting the table to readonly, so as to trigger an exception whenever writing is attempted.
 
Not sure if my analysis is correct?
 
Thanks.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel