Re: [PATCH v3 1/2] memory-hotplug: introduce CONFIG_HAVE_BOOTMEM_INFO_NODE and revert register_page_bootmem_info_node() when platform not support

2013-01-17 Thread Lin Feng
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

Re: [PATCH v3 1/2] memory-hotplug: introduce CONFIG_HAVE_BOOTMEM_INFO_NODE and revert register_page_bootmem_info_node() when platform not support

2013-01-17 Thread Michal Hocko
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 register_page_bootmem_info_node() is defined in > CONFIG_MEM

Re: [PATCH v3 1/2] memory-hotplug: introduce CONFIG_HAVE_BOOTMEM_INFO_NODE and revert register_page_bootmem_info_node() when platform not support

2013-01-17 Thread Lin Feng
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

Re: [PATCH v3 1/2] memory-hotplug: introduce CONFIG_HAVE_BOOTMEM_INFO_NODE and revert register_page_bootmem_info_node() when platform not support

2013-01-16 Thread Michal Hocko
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 a whole node. > Say N here if you want kernel

[PATCH v3 1/2] memory-hotplug: introduce CONFIG_HAVE_BOOTMEM_INFO_NODE and revert register_page_bootmem_info_node() when platform not support

2013-01-16 Thread Lin Feng
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 Signed-off-by: Lin Feng --- ChangeLog v2->v3: - Rename the patch title to