WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, Jan Beulich <jbeulich@xxxxxxxxxx>, Tim Deegan <Tim.Deegan@xxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] RE: [PATCH 2/6] Change the boot allocator function to support memory add
From: "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>
Date: Sun, 28 Jun 2009 21:59:25 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc:
Delivery-date: Sun, 28 Jun 2009 07:00:01 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C66D321C.E596%keir.fraser@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <E2263E4A5B2284449EEBD0AAB751098402CCF824F3@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <C66D321C.E596%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acn30qSePbAyG89HR16wSczYgDMjIQAAzbqgAAIDDVAABiKE1wAAItCg
Thread-topic: [PATCH 2/6] Change the boot allocator function to support memory add

>-----Original Message-----
>From: Keir Fraser [mailto:keir.fraser@xxxxxxxxxxxxx] 
>Sent: 2009年6月28日 21:44
>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:24, "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx> wrote:
>
>>> The undelrying implementation ideas may be okay, but calling these
>>> extensions to the 'boot allocator' makes no sense. The boot
>>> allocator only
>>> exists during boot. The fact that the bitmap it uses persists
>>> beyond boot is
>>> an implementation detail. Perhaps you just need to change the
>> 
>> So can I understand the allocator bitmap (i.e. those for 
>map_free/map_call) as
>> something not just about boot allocator, but for generic 
>bitmap to remember
>> the page allocation status?
>> Maybe we can just using one bit in page_info to indicate if 
>page is allocated
>> in future?
>
>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.

Shall our patch wait for your changes and do rebase, or shall I still working 
on the re-name method (I suspect the previous re-name patch may not be so 
important if we have this changes)?

Thanks
Yunhong Jiang

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