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

[Xen-devel] Dom0 initial memory map guarantees

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Dom0 initial memory map guarantees
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Mon, 30 Mar 2009 10:10:16 +0100
Delivery-date: Mon, 30 Mar 2009 02:36:04 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
While for DomU's the initial memory map clearly cannot be expected to be
contiguous in MFN space, currently it happens to be that way for (x86)
Dom0 (and even the !NDEBUG case only intentionally breaks this for the
space beyond v_end).

Without a formal guarantee it would seem fragile, however, to rely on
this. Thus the question is whether it's reasonable to document such a
behavior, or whether instead any such assumption should be forcefully
broken by the Dom0 builder.

Thanks, Jan


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

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