From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Xenheap disappearance: (was: xen_phys_start for 32b) Date: Thu, 08 Jan 2009 09:04:17 +0000 Message-ID: References: <431159ad-21d8-43bf-b9a1-2d554b92589a@default> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <431159ad-21d8-43bf-b9a1-2d554b92589a@default> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Dan Magenheimer , xen-devel@lists.xensource.com Cc: "Cihula, Joseph" List-Id: xen-devel@lists.xenproject.org On 08/01/2009 00:17, "Dan Magenheimer" wrote: >> Xenheap will disappear entirely on x86/64 in future. So long >> term is that >> i386 and x86/64 are actually to diverge significantly in this area. > > What's the ETA on this? I've got a big patch in preparation built > on 3.3. that does gymnastics to get around xenheap limitations > and have been holding off updating it to unstable, hoping for > this xenheap change (to avoid re-re-duplicating the wheel). How difficult has it been to work around? Is it just pointing xmalloc() at the domheap instead of xenheap? -- Keir