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: Memory hot-add and c/s 20892: bad interaction?

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx>
Subject: [Xen-devel] RE: Memory hot-add and c/s 20892: bad interaction?
From: "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>
Date: Tue, 9 Feb 2010 13:33:21 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 08 Feb 2010 21:33:45 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C795A29E.96A4%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: <4B6FFEEF020000780002E3C5@xxxxxxxxxxxxxxxxxx> <C795A29E.96A4%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acqoryvt0Oh12L7RTUe8zHJJYT73PQAALr7lACZP0FA=
Thread-topic: Memory hot-add and c/s 20892: bad interaction?
Keir/Jan, thanks for your notice.

Thanks
--jyh

>-----Original Message-----
>From: Keir Fraser [mailto:keir.fraser@xxxxxxxxxxxxx]
>Sent: Monday, February 08, 2010 7:15 PM
>To: Jan Beulich; Jiang, Yunhong
>Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
>Subject: Re: Memory hot-add and c/s 20892: bad interaction?
>
>On 08/02/2010 11:09, "Jan Beulich" <JBeulich@xxxxxxxxxx> wrote:
>
>>> I was wondering whether this changeset is actually a bad idea in light of
>>> memory hot-add, as now implemented by Yunhong? I would imagine this can
>mean
>>> that max_mfn is now dynamic, and can increase in value after boot. So would
>>> 20892 thus leave all existing guests (e.g., dom0!) broken after a hot-add
>>> which adds new highest RAM addresses?
>>
>> You probably overlooked the
>>
>> +        if ( !mem_hotplug )
>
>Yeah, I looked at the changeset comment and not the patch itself! Sorry
>about that.
>
> -- Keir
>


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

<Prev in Thread] Current Thread [Next in Thread>