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] Re: Xenheap disappearance: (was: xen_phys_start for 32b)

To: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Re: Xenheap disappearance: (was: xen_phys_start for 32b)
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Thu, 15 Jan 2009 08:38:37 +0000
Cc:
Delivery-date: Thu, 15 Jan 2009 00:38:38 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <414df624-72b4-4367-aa38-979286b39a88@default>
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
Thread-index: Acl27KidK519fkPPUkSeILnypK8P/A==
Thread-topic: Xenheap disappearance: (was: xen_phys_start for 32b)
User-agent: Microsoft-Entourage/12.15.0.081119
On 14/01/2009 22:45, "Dan Magenheimer" <dan.magenheimer@xxxxxxxxxx> wrote:

> Thinking about this a bit more, unless you plan to stop
> supporting 32-bit Xen anytime soon, the semantic differences
> probably warrant adding a second interface, let's call
> it admalloc() (ad == anonymous domain), that should only be
> used in 64-bit-only code where it can be guaranteed that
> usage of pointers to the alloc'ed memory need not be bracketed
> with (ugly) map/unmap_domain_page() calls.
> 
> So I'd suggest adding _admalloc() and adfree() to xmalloc_tlsf.c
> and when ifdef x86_64, _xmalloc and xfree simply get redefined
> to _admalloc/adfree in xmalloc_tlsf.h.
> 
> If this sounds sensible, I will spin a patch as I'm the one keen
> to get this settled.

Xmalloc/xfree can use alloc_domheap_pages always on x86/64. A temporary
ifdef inside xmalloc is better than an extra xmalloc interface.

 -- Keir



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

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