Re: [RFC PATCH v4 7/13] memory-hotplug : remove_memory calls __remove_pages

2012-07-19 Thread Bob Liu
On Wed, Jul 18, 2012 at 6:12 PM, Yasuaki Ishimatsu wrote: > The patch adds __remove_pages() to remove_memory(). Then the range of > phys_start_pfn argument and nr_pages argument in __remove_pagse() may > have different zone. So zone argument is removed from __remove_pages() > and __remove_pages()

Re: [RFC PATCH v4 7/13] memory-hotplug : remove_memory calls __remove_pages

2012-07-19 Thread Yasuaki Ishimatsu
Hi Bob, 2012/07/19 17:32, Bob Liu wrote: On Wed, Jul 18, 2012 at 6:12 PM, Yasuaki Ishimatsu wrote: The patch adds __remove_pages() to remove_memory(). Then the range of phys_start_pfn argument and nr_pages argument in __remove_pagse() may have different zone. So zone argument is removed from _

[RFC PATCH v4 7/13] memory-hotplug : remove_memory calls __remove_pages

2012-07-18 Thread Yasuaki Ishimatsu
The patch adds __remove_pages() to remove_memory(). Then the range of phys_start_pfn argument and nr_pages argument in __remove_pagse() may have different zone. So zone argument is removed from __remove_pages() and __remove_pages() caluculates zone in each section. When CONFIG_SPARSEMEM_VMEMMAP is