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/
Home Products Support Community News


[Xen-devel] Move MEMZONE_XEN to the last

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: [Xen-devel] Move MEMZONE_XEN to the last
From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date: Wed, 21 Mar 2007 13:56:58 +0800
Cc: "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>
Delivery-date: Tue, 20 Mar 2007 22:56:04 -0700
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
Thread-index: AcdrfbxSnJLS4ENvSZCWOz4WCGzqkw==
Thread-topic: Move MEMZONE_XEN to the last
Zone index for domain heap is derived from bits, while zone index for 
xen heap takes 0 to catch all. This looks a bit messed which prevents 
future extension. For example, if Xen can be located at higher memory:
        - The assumption that domheap starts from MEMZONE_XEN+1 
doesn't hold true
        - The memory within the very bit but out of xenheap can't be 
claimed by domheap since that bit belongs to xenheap exclusively

So how about moving MEMZONE_XEN to the last 
(current NR_ZONES plus 1)? That can ensure domheap covering all
possible bits exactly. 


Xen-devel mailing list

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