Xen 
 
Home About Xen.org Xen Xen Summit Wiki Mailing List Bug Tracker Xen Downloads
 
   
 

xense-devel

[Xense-devel] Xen memory management

To: <xense-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xense-devel] Xen memory management
From: "Myong H. Kang" <mkang@xxxxxxxxxxxxxxxx>
Date: Thu, 16 Feb 2006 09:14:38 -0500
Delivery-date: Thu, 16 Feb 2006 14:28:50 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
Importance: Normal
List-help: <mailto:xense-devel-request@lists.xensource.com?subject=help>
List-id: "A discussion list for those developing security enhancements for Xen." <xense-devel.lists.xensource.com>
List-post: <mailto:xense-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xense-devel>, <mailto:xense-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xense-devel>, <mailto:xense-devel-request@lists.xensource.com?subject=unsubscribe>
Reply-to: mkang@xxxxxxxxxxxxxxxx
Sender: xense-devel-bounces@xxxxxxxxxxxxxxxxxxx
Dear Xen experts,

I have some naïve questions about Xen memory management. 

Xen interface manual describes the following:
"Xen maintains a globally readable machine-to-physical table which
records the mapping from machine page frames to pseudo-physical ones."

The questions are: 
What does it mean by "globally readable"? Which hypercall is being used to
access this table from a guest domain (or is there some other way to access
this table from a guest domain)?
Is it possible to read memory content of guest domain B (or domain 0) from
guest domain A? 

 
Thanks,

Myong  




_______________________________________________
Xense-devel mailing list
Xense-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xense-devel

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