From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Magenheimer Subject: RE: Xenheap disappearance: (was: xen_phys_start for 32b) Date: Wed, 14 Jan 2009 22:45:15 +0000 (GMT) Message-ID: <414df624-72b4-4367-aa38-979286b39a88@default> References: Mime-Version: 1.0 Content-Type: text/plain; charset=Windows-1252 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org > How difficult has it been to work around? Is it just pointing=20 > xmalloc() at > the domheap instead of xenheap? >=20 > -- Keir 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 =3D=3D 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. Thanks, Dan