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

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

>-----Original Message-----
>From: Keir Fraser [mailto:keir.fraser@xxxxxxxxxxxxx] 
>Sent: 2009年6月28日 23:38
>To: Jiang, Yunhong; Jan Beulich; Tim Deegan; 
>xen-devel@xxxxxxxxxxxxxxxxxxx
>Subject: Re: [PATCH 2/6] Change the boot allocator function to 
>support memory add
>
>On 28/06/2009 14:59, "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx> wrote:
>
>>> I think the PGC_ flags could be extended to do this, yes.
>>> Maybe I will look
>>> into that.
>> 
>> Thanks. We try to do this way in the beginning , but in the 
>end gives up
>> because currently too many direct operation to count_info 
>without any macro
>> wrapper, and I'm not confident to take over ALL of them.
>
>This should already have been dealt with when 
>PGC_offlining/broken/offlined

Yes, I remember I did some cleanup on it before :$

>were added. Thus I think it should be straightforward to make 
>the change.
>Also this flag would only be set for pages which belong to the page
>allocator. Noone else would ever set the flag since they do 
>not own the bit.
>So I think the patch is straightforward to construct.
>
>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()?

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.

Thanks
Yunhong Jiang

>hardly anyone uses it. That will just require some care in 
>bringing up the
>frametable and its mappings, which the main allocator is dependent on.
>
> -- Keir
>
>
>

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