| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
[Xen-devel] Re: [PATCH V3] xen/balloon: Memory hotplug support for Xen b
|
To: |
"v.tolstov@xxxxxxxxx" <v.tolstov@xxxxxxxxx> |
|
Subject: |
[Xen-devel] Re: [PATCH V3] xen/balloon: Memory hotplug support for Xen balloon driver |
|
From: |
Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx> |
|
Date: |
Wed, 18 May 2011 08:21:49 +0100 |
|
Cc: |
"jeremy@xxxxxxxx" <jeremy@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "haicheng.li@xxxxxxxxxxxxxxx" <haicheng.li@xxxxxxxxxxxxxxx>, "konrad.wilk@xxxxxxxxxx" <konrad.wilk@xxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, "dave@xxxxxxxxxxxxxxxxxx" <dave@xxxxxxxxxxxxxxxxxx>, "linux-mm@xxxxxxxxx" <linux-mm@xxxxxxxxx>, "wdauchy@xxxxxxxxx" <wdauchy@xxxxxxxxx>, "rientjes@xxxxxxxxxx" <rientjes@xxxxxxxxxx>, "andi.kleen@xxxxxxxxx" <andi.kleen@xxxxxxxxx>, "akpm@xxxxxxxxxxxxxxxxxxxx" <akpm@xxxxxxxxxxxxxxxxxxxx>, "fengguang.wu@xxxxxxxxx" <fengguang.wu@xxxxxxxxx>, Daniel Kiper <dkiper@xxxxxxxxxxxx> |
|
Delivery-date: |
Wed, 18 May 2011 00:22:32 -0700 |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<1305701868.28175.1.camel@vase> |
|
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> |
|
Organization: |
Citrix Systems, Inc. |
|
References: |
<20110517214421.GD30232@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <1305701868.28175.1.camel@vase> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
On Wed, 2011-05-18 at 07:57 +0100, Vasiliy G Tolstov wrote:
> On Tue, 2011-05-17 at 23:44 +0200, Daniel Kiper wrote:
> > + Memory could be hotplugged in following steps:
> > +
> > + 1) dom0: xl mem-max <domU> <maxmem>
> > + where <maxmem> is >= requested memory size,
> > +
> > + 2) dom0: xl mem-set <domU> <memory>
> > + where <memory> is requested memory size; alternatively memory
> > + could be added by writing proper value to
> > + /sys/devices/system/xen_memory/xen_memory0/target or
> > + /sys/devices/system/xen_memory/xen_memory0/target_kb on dumU,
> > +
> > + 3) domU: for i in /sys/devices/system/memory/memory*/state; do \
> > + [ "`cat "$i"`" = offline ] && echo online > "$i"; done
> > +
> Very good. Is that possible to eliminate step 3 ? And do it automatic if
> domU runs with specific xen balloon param?
When we faced the same question WRT VCPU hotplug we ended up using a
udev rule. Presumably the same could be done here. In the VCPU case the
rule is:
ACTION=="add", SUBSYSTEM=="cpu", RUN+="/bin/sh -c '[ ! -e /sys$devpath/online ]
|| echo 1 > /sys$devpath/online'"
Presumably the memory one will be broadly similar.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home