RE: [Xen-devel] Re: [PATCH 2/6] Change the boot allocator function to support memory add

["Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>]

xen-devel-bounces@xxxxxxxxxxxxxxxxxxx wrote:
> On 29/06/2009 03:04, "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx> wrote:
> 
>>> Actually it'd be nice to get rid of the allocator bitmap
>>> altogether, since
>> 
>> I checked the code and seems the main caller is map_pages_to_xen().
>> So do you mean you will setup the frametable earlier, so that all
>> page allocator will use the main allocator, even in
>> map_pages_to_xen()? 
> 
> I would have it go steal pages from boot_e820 directly I think.
> 
>> For memory add, it may be a bit different. The new pages should not
>> be in main allocator before the m2p table is setup (in boot stage,
>> the m2p will not be used till construct dom0, so it is ok) , also we
>> may want to use the new memory as the page table when setup the m2p
>> table. 
> 
> Well, I assume you will code up something special for that.
> That seems to
> have nothing to do with whether we keep the boot-time allocator, and
> allocation bitmap, or not. 

Yes, I'd steal some pages from the added memory. There is not much difference 
with the map_pages_to_xen() in booting stage.

--jyh

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