[Top] [All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

  • To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Peter Teoh" <htmldeveloper@xxxxxxxxx>
  • Date: Wed, 12 Sep 2007 11:15:02 +0800
  • Delivery-date: Tue, 11 Sep 2007 20:15:41 -0700
  • 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=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
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

 

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.

Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.