Hi Michal,
On 01/16/2013 10:14 PM, Michal Hocko wrote:
On Wed 16-01-13 16:14:18, Lin Feng wrote:
[...]
diff --git a/mm/Kconfig b/mm/Kconfig
index 278e3ab..f8c5799 100644
--- a/mm/Kconfig
+++ b/mm/Kconfig
@@ -162,10 +162,18 @@ config MOVABLE_NODE
Say Y here if you want to hotplug
Hi Michal,
On 01/17/2013 09:05 PM, Michal Hocko wrote:
On Thu 17-01-13 18:37:10, Lin Feng wrote:
[...]
I am still not sure I understand the relation to MEMORY_HOTREMOVE.
Is register_page_bootmem_info_node required/helpful even if
!CONFIG_MEMORY_HOTREMOVE?
From old kenrel's view
added, remove unimplemented functions suggested by Michal.
ChangeLog v1-v2:
1) patch 1/2:
- Add a Kconfig option named HAVE_BOOTMEM_INFO_NODE suggested by Michal, which
will be automatically selected by supported archs(currently only on x86_64).
Lin Feng (1):
memory-hotplug: revert
It's implemented by adding a new Kconfig option named
CONFIG_HAVE_BOOTMEM_INFO_NODE, which will be automatically selected by
memory-hotplug feature fully supported archs(currently only on x86_64).
Reported-by: Michal Hocko mho...@suse.cz
Signed-off-by: Lin Feng linf...@cn.fujitsu.com
() and flesh out from top to
end.
Signed-off-by: Michal Hocko mho...@suse.cz
Signed-off-by: Lin Feng linf...@cn.fujitsu.com
---
arch/ia64/mm/discontig.c |5 -
arch/powerpc/mm/init_64.c |5 -
arch/s390/mm/vmem.c |6 --
arch/sparc/mm/init_64.c |5 -
4 files
