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] [PATCH 0/4] domain heap allocator changes

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] [PATCH 0/4] domain heap allocator changes
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Wed, 07 Feb 2007 17:09:27 +0000
Delivery-date: Wed, 07 Feb 2007 09:06:45 -0800
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
In order to (longer term) constrain 32-bit pv domains running on 64-bit hv to
physical memory addresses it can actually control (namely use the m2p map
on) without also limiting the amount (and range) of memory accessible to
64-bit domains, the following four patches will change the allocator so that
a per-domain address size restriction can be established.

A positive side effect of this is that there no longer is a need to constrain
DMA addresses to 30 bits (there's not going to be a DMA heap anymore),
as by default memory will now be allocated from addresses above the DMA
boundary (which is now purely for determining within what range memory
should, if at all, be reserved, but not to artificially limit I/O-capable in 
what
memory they are permitted to request), and could go away entirely if there
wasn't the need to set aside some sufficiently low-address memory for the
dom0 swiotlb), so setting the boundary to the more conventional 32 bits
will still result in more constrained allocations to succeed (as long as there's
memory meeting the constraint).

All patches have only been tested on x86.

Jan

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] [PATCH 0/4] domain heap allocator changes, Jan Beulich <=