Reza Arbab <arbab@xxxxxxxxxxxxxxxxxx> writes: > To create a movable node, we need to hotplug all of its memory into > ZONE_MOVABLE. > > Note that to do this, auto_online_blocks should be off. Since the memory > will first be added to the default zone, we must explicitly use > online_movable to online. > > Because such a node contains no normal memory, can_online_high_movable() > will only allow us to do the onlining if CONFIG_MOVABLE_NODE is set. > Enable the use of this config option on PPC64 platforms. > Reviewed-by: Aneesh Kumar K.V <aneesh.kumar@xxxxxxxxxxxxxxxxxx> > Signed-off-by: Reza Arbab <arbab@xxxxxxxxxxxxxxxxxx> > --- > Documentation/kernel-parameters.txt | 2 +- > mm/Kconfig | 2 +- > 2 files changed, 2 insertions(+), 2 deletions(-) > > diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt > index a4f4d69..3d8460d 100644 > --- a/Documentation/kernel-parameters.txt > +++ b/Documentation/kernel-parameters.txt > @@ -2344,7 +2344,7 @@ bytes respectively. Such letter suffixes can also be entirely omitted. > that the amount of memory usable for all allocations > is not too small. > > - movable_node [KNL,X86] Boot-time switch to enable the effects > + movable_node [KNL,X86,PPC] Boot-time switch to enable the effects > of CONFIG_MOVABLE_NODE=y. See mm/Kconfig for details. > > MTD_Partition= [MTD] > diff --git a/mm/Kconfig b/mm/Kconfig > index be0ee11..4b19cd3 100644 > --- a/mm/Kconfig > +++ b/mm/Kconfig > @@ -153,7 +153,7 @@ config MOVABLE_NODE > bool "Enable to assign a node which has only movable memory" > depends on HAVE_MEMBLOCK > depends on NO_BOOTMEM > - depends on X86_64 > + depends on X86_64 || PPC64 > depends on NUMA > default n > help > -- > 1.8.3.1 -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
