On 2014/8/19 5:48, David Rientjes wrote: > On Wed, 13 Aug 2014, Zhang Zhen wrote: > >> Currently memory-hotplug has two limits: >> 1. If the memory block is in ZONE_NORMAL, you can change it to >> ZONE_MOVABLE, but this memory block must be adjacent to ZONE_MOVABLE. >> 2. If the memory block is in ZONE_MOVABLE, you can change it to >> ZONE_NORMAL, but this memory block must be adjacent to ZONE_NORMAL. >> >> With this patch, we can easy to know a memory block can be onlined to >> which zone, and don't need to know the above two limits. >> >> Updated the related Documentation. >> >> Change v1 -> v2: >> - optimize the implementation following Dave Hansen's suggestion >> >> Signed-off-by: Zhang Zhen <zhenzhang.zh...@huawei.com> > > linux-next build failure: > > drivers/built-in.o: In function `show_zones_online_to': > memory.c:(.text+0x13ee09): undefined reference to `test_pages_in_a_zone' > The function implementation in mm/memory_hotplug.c is only built if CONFIG_MEMORY_HOTREMOVE is enabled.
A fix has been proposed. http://ozlabs.org/~akpm/mmots/broken-out/memory-hotplug-add-sysfs-zones_online_to-attribute-fix-2.patch Thanks! > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
