linux-kernel - Re: [PATCH V3] xen/balloon: Memory hotplug support for Xen balloon driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 18 May 2011 10:57:48 +0400
From:	Vasiliy G Tolstov <v.tolstov@...fip.ru>
To:	Daniel Kiper <dkiper@...-space.pl>
Cc:	ian.campbell@...rix.com, akpm@...ux-foundation.org,
	andi.kleen@...el.com, haicheng.li@...ux.intel.com,
	fengguang.wu@...el.com, jeremy@...p.org, konrad.wilk@...cle.com,
	dan.magenheimer@...cle.com, pasik@....fi, dave@...ux.vnet.ibm.com,
	wdauchy@...il.com, rientjes@...gle.com,
	xen-devel@...ts.xensource.com, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org
Subject: Re: [PATCH V3] xen/balloon: Memory hotplug support for Xen balloon
 driver

On Tue, 2011-05-17 at 23:44 +0200, Daniel Kiper wrote:
> This patch applies to Linus' git tree, v2.6.39-rc7 tag with a few
> prerequisite patches available at https://lkml.org/lkml/2011/5/17/407
> and at https://lkml.org/lkml/2011/3/28/98.
> 
> Memory hotplug support for Xen balloon driver. It should be
> mentioned that hotplugged memory is not onlined automatically.
> It should be onlined by user through standard sysfs interface.
> 
> 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
> 
> Signed-off-by: Daniel Kiper <dkiper@...-space.pl>
> Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
> ---
>  drivers/xen/Kconfig   |   24 +++++++++
>  drivers/xen/balloon.c |  139 ++++++++++++++++++++++++++++++++++++++++++++++++-
>  include/xen/balloon.h |    4 ++
>  3 files changed, 165 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/xen/Kconfig b/drivers/xen/Kconfig
> index a59638b..b74501e 100644
> --- a/drivers/xen/Kconfig
> +++ b/drivers/xen/Kconfig
> @@ -9,6 +9,30 @@ config XEN_BALLOON
>  	  the system to expand the domain's memory allocation, or alternatively
>  	  return unneeded memory to the system.
>  
> +config XEN_BALLOON_MEMORY_HOTPLUG
> +	bool "Memory hotplug support for Xen balloon driver"
> +	default n
> +	depends on XEN_BALLOON && MEMORY_HOTPLUG
> +	help
> +	  Memory hotplug support for Xen balloon driver allows expanding memory
> +	  available for the system above limit declared at system startup.
> +	  It is very useful on critical systems which require long
> +	  run without rebooting.
> +
> +	  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?

-- 
> 
> Vasiliy G Tolstov <v.tolstov@...fip.ru>
> Selfip.Ru

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/