From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: New heap API and scrubbing Date: Tue, 10 Feb 2009 05:19:11 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit 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: Dan Magenheimer , "Xen-Devel (E-mail)" List-Id: xen-devel@lists.xenproject.org They allocate from the same pool of pages, but they differ very slightly. If you alloc_fooheap_pages() you must free_fooheap_pages(). You could probably make the distinction based on is_xenheap_page() if you wanted. -- Keir On 10/02/2009 00:24, "Dan Magenheimer" wrote: > So in the new (soon-to-be 3.4) heap API, are > > alloc_domheap_pages(NULL,order,flags) > > and > > alloc_xenheap_pages(order,flags) > > synonomous on 64-bit hypervisors? I.e. they > are allocating from the same pool of pages? > And if so are the matching free routines > synonomous? > > If not, under what circumstances should one be > used rather than the other? > > Are there any cases now where free_XXXheap_pages > might free up pages that could be grabbed by > another domain and those pages have not been > scrubbed? > > Thanks, > Dan > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel