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/
Home Products Support Community News


[Xen-devel] RE: [PATCH v2.0 1/6] Add a config option for memory hot add

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx>
Subject: [Xen-devel] RE: [PATCH v2.0 1/6] Add a config option for memory hot add
From: "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>
Date: Wed, 8 Jul 2009 22:31:25 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 08 Jul 2009 07:32:41 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C67A5E92.9189%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: <E2263E4A5B2284449EEBD0AAB751098402CD10B469@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <C67A5E92.9189%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acn/n+A3yJUALD5FQNSIqtARBUwsjgAMLZJkAAHSpaA=
Thread-topic: [PATCH v2.0 1/6] Add a config option for memory hot add
Keir Fraser wrote:
> On 08/07/2009 08:44, "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx> wrote:
>> This patch add an option for memory hot add.
>> Signed-off-by: Jiang, Yunhong <yunhong.jiang@xxxxxxxxx>
> Doesn't need to be a config option. We only have some CONFIG_*
> options to
> avoid modifying Linux-derived files. For new Xen features,
> don't bother. Add
> X86_MAX_PFN in the patch that uses it, and if it is x86_32 only then
> it should only be defined for that build target (not x86_64 as well).

Sorry that I didn't realize the purpose of the CONFIG_* options. But this 
optoin may be needed because:
a) When memory hotplug, we need set the boot allocation bitmap memory to 512k 
when booting. So for small system, we can avoid that extra memory. Of course, 
maybe that can be removed after the allocation bitmap is removed al-together.
b) When Memory hotplug, we can't adjust compatible guest's hv_virt_start 
anymore. I'm not sure how important it is, so I keep that for 
non-memory-hotplug support.

Any idea?

I will change the X86_MAX_PFN.

> -- Keir
Xen-devel mailing list