Linux ACPI Development Discussion List

Yasuaki Ishimatsu | 9 Jul 2012 12:21

[RFC PATCH v3 0/13] memory-hotplug : hot-remove physical memory

This patch series aims to support physical memory hot-remove.

  [RFC PATCH v3 1/13] memory-hotplug : rename remove_memory to offline_memory
  [RFC PATCH v3 2/13] memory-hotplug : add physical memory hotplug code to acpi_memory_device_remove
  [RFC PATCH v3 3/13] memory-hotplug : unify argument of firmware_map_add_early/hotplug
  [RFC PATCH v3 4/13] memory-hotplug : remove /sys/firmware/memmap/X sysfs
  [RFC PATCH v3 5/13] memory-hotplug : does not release memory region in PAGES_PER_SECTION chunks
  [RFC PATCH v3 6/13] memory-hotplug : add memory_block_release
  [RFC PATCH v3 7/13] memory-hotplug : remove_memory calls __remove_pages
  [RFC PATCH v3 8/13] memory-hotplug : check page type in get_page_bootmem
  [RFC PATCH v3 9/13] memory-hotplug : move register_page_bootmem_info_node and put_page_bootmem for
sparse-vmemmap
  [RFC PATCH v3 10/13] memory-hotplug : implement register_page_bootmem_info_section of sparse-vmemmap
  [RFC PATCH v3 11/13] memory-hotplug : free memmap of sparse-vmemmap
  [RFC PATCH v3 12/13] memory-hotplug : add node_device_release
  [RFC PATCH v3 13/13] memory-hotplug : remove sysfs file of node

Even if you apply these patches, you cannot remove the physical memory
completely since these patches are still under development. I want you to
cooperate to improve the physical memory hot-remove. So please review these
patches and give your comment/idea.

The patches can free/remove following things:

  - acpi_memory_info                          : [RFC PATCH 2/13]
  - /sys/firmware/memmap/X/{end, start, type} : [RFC PATCH 4/13]
  - iomem_resource                            : [RFC PATCH 5/13]
  - mem_section and related sysfs files       : [RFC PATCH 6-11/13]
  - node and related sysfs files              : [RFC PATCH 12-13/13]

(Continue reading)

headers

Yasuaki Ishimatsu | 9 Jul 2012 12:23

[RFC PATCH v3 1/13] memory-hotplug : rename remove_memory to offline_memory

remove_memory() does not remove memory but just offlines memory. The patch
changes name of it to offline_memory().

CC: David Rientjes <rientjes <at> google.com>
CC: Jiang Liu <liuj97 <at> gmail.com>
CC: Len Brown <len.brown <at> intel.com>
CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
CC: Paul Mackerras <paulus <at> samba.org>
CC: Christoph Lameter <cl <at> linux.com>
Cc: Minchan Kim <minchan.kim <at> gmail.com>
CC: Andrew Morton <akpm <at> linux-foundation.org>
CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
CC: Wen Congyang <wency <at> cn.fujitsu.com>
Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>

---
 drivers/acpi/acpi_memhotplug.c |    2 +-
 drivers/base/memory.c          |    4 ++--
 include/linux/memory_hotplug.h |    2 +-
 mm/memory_hotplug.c            |    6 +++---
 4 files changed, 7 insertions(+), 7 deletions(-)

Index: linux-3.5-rc4/drivers/acpi/acpi_memhotplug.c
===================================================================
--- linux-3.5-rc4.orig/drivers/acpi/acpi_memhotplug.c	2012-07-03 14:21:46.102416917 +0900
+++ linux-3.5-rc4/drivers/acpi/acpi_memhotplug.c	2012-07-03 14:21:49.458374960 +0900
 <at>  <at>  -318,7 +318,7  <at>  <at>  static int acpi_memory_disable_device(st
 	 */
 	list_for_each_entry_safe(info, n, &mem_device->res_list, list) {
 		if (info->enabled) {

(Continue reading)

headers

Yasuaki Ishimatsu | 9 Jul 2012 12:23

[RFC PATCH v3 1/13] memory-hotplug : rename remove_memory to offline_memory

remove_memory() does not remove memory but just offlines memory. The patch
changes name of it to offline_memory().

CC: David Rientjes <rientjes <at> google.com>
CC: Jiang Liu <liuj97 <at> gmail.com>
CC: Len Brown <len.brown <at> intel.com>
CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
CC: Paul Mackerras <paulus <at> samba.org>
CC: Christoph Lameter <cl <at> linux.com>
Cc: Minchan Kim <minchan.kim <at> gmail.com>
CC: Andrew Morton <akpm <at> linux-foundation.org>
CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
CC: Wen Congyang <wency <at> cn.fujitsu.com>
Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>

---
 drivers/acpi/acpi_memhotplug.c |    2 +-
 drivers/base/memory.c          |    4 ++--
 include/linux/memory_hotplug.h |    2 +-
 mm/memory_hotplug.c            |    6 +++---
 4 files changed, 7 insertions(+), 7 deletions(-)

Index: linux-3.5-rc4/drivers/acpi/acpi_memhotplug.c
===================================================================
--- linux-3.5-rc4.orig/drivers/acpi/acpi_memhotplug.c	2012-07-03 14:21:46.102416917 +0900
+++ linux-3.5-rc4/drivers/acpi/acpi_memhotplug.c	2012-07-03 14:21:49.458374960 +0900
 <at>  <at>  -318,7 +318,7  <at>  <at>  static int acpi_memory_disable_device(st
 	 */
 	list_for_each_entry_safe(info, n, &mem_device->res_list, list) {
 		if (info->enabled) {

(Continue reading)

headers

Yasuaki Ishimatsu | 9 Jul 2012 12:24

[RFC PATCH v3 2/13] memory-hotplug : add physical memory hotplug code to acpi_memory_device_remove

acpi_memory_device_remove() has been prepared to remove physical memory.
But, the function only frees acpi_memory_device currentlry.

The patch adds following functions into acpi_memory_device_remove():
  - offline memory
  - remove physical memory (only return -EBUSY)
  - free acpi_memory_device

CC: David Rientjes <rientjes <at> google.com>
CC: Jiang Liu <liuj97 <at> gmail.com>
CC: Len Brown <len.brown <at> intel.com>
CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
CC: Paul Mackerras <paulus <at> samba.org>
CC: Christoph Lameter <cl <at> linux.com>
Cc: Minchan Kim <minchan.kim <at> gmail.com>
CC: Andrew Morton <akpm <at> linux-foundation.org>
CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
CC: Wen Congyang <wency <at> cn.fujitsu.com>
Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>

---
 drivers/acpi/acpi_memhotplug.c |   26 +++++++++++++++++++++++++-
 drivers/base/memory.c          |   39 +++++++++++++++++++++++++++++++++++++++
 include/linux/memory.h         |    5 +++++
 include/linux/memory_hotplug.h |    1 +
 mm/memory_hotplug.c            |    8 ++++++++
 5 files changed, 78 insertions(+), 1 deletion(-)

Index: linux-3.5-rc6/drivers/acpi/acpi_memhotplug.c
===================================================================

(Continue reading)

headers

Wen Congyang | 13 Jul 2012 05:26

Re: [RFC PATCH v3 2/13] memory-hotplug : add physical memory hotplug code to acpi_memory_device_remove

At 07/09/2012 06:24 PM, Yasuaki Ishimatsu Wrote:
> acpi_memory_device_remove() has been prepared to remove physical memory.
> But, the function only frees acpi_memory_device currentlry.
> 
> The patch adds following functions into acpi_memory_device_remove():
>   - offline memory
>   - remove physical memory (only return -EBUSY)
>   - free acpi_memory_device
> 
> CC: David Rientjes <rientjes <at> google.com>
> CC: Jiang Liu <liuj97 <at> gmail.com>
> CC: Len Brown <len.brown <at> intel.com>
> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
> CC: Paul Mackerras <paulus <at> samba.org>
> CC: Christoph Lameter <cl <at> linux.com>
> Cc: Minchan Kim <minchan.kim <at> gmail.com>
> CC: Andrew Morton <akpm <at> linux-foundation.org>
> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
> CC: Wen Congyang <wency <at> cn.fujitsu.com>
> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>
> 
> ---
>  drivers/acpi/acpi_memhotplug.c |   26 +++++++++++++++++++++++++-
>  drivers/base/memory.c          |   39 +++++++++++++++++++++++++++++++++++++++
>  include/linux/memory.h         |    5 +++++
>  include/linux/memory_hotplug.h |    1 +
>  mm/memory_hotplug.c            |    8 ++++++++
>  5 files changed, 78 insertions(+), 1 deletion(-)
> 
> Index: linux-3.5-rc6/drivers/acpi/acpi_memhotplug.c

(Continue reading)

headers

Yasuaki Ishimatsu | 17 Jul 2012 02:46

Re: [RFC PATCH v3 2/13] memory-hotplug : add physical memory hotplug code to acpi_memory_device_remove

Hi Wen,

2012/07/13 12:26, Wen Congyang wrote:
> At 07/09/2012 06:24 PM, Yasuaki Ishimatsu Wrote:
>> acpi_memory_device_remove() has been prepared to remove physical memory.
>> But, the function only frees acpi_memory_device currentlry.
>>
>> The patch adds following functions into acpi_memory_device_remove():
>>    - offline memory
>>    - remove physical memory (only return -EBUSY)
>>    - free acpi_memory_device
>>
>> CC: David Rientjes <rientjes <at> google.com>
>> CC: Jiang Liu <liuj97 <at> gmail.com>
>> CC: Len Brown <len.brown <at> intel.com>
>> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
>> CC: Paul Mackerras <paulus <at> samba.org>
>> CC: Christoph Lameter <cl <at> linux.com>
>> Cc: Minchan Kim <minchan.kim <at> gmail.com>
>> CC: Andrew Morton <akpm <at> linux-foundation.org>
>> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
>> CC: Wen Congyang <wency <at> cn.fujitsu.com>
>> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>
>>
>> ---
>>   drivers/acpi/acpi_memhotplug.c |   26 +++++++++++++++++++++++++-
>>   drivers/base/memory.c          |   39 +++++++++++++++++++++++++++++++++++++++
>>   include/linux/memory.h         |    5 +++++
>>   include/linux/memory_hotplug.h |    1 +
>>   mm/memory_hotplug.c            |    8 ++++++++

(Continue reading)

headers

Yasuaki Ishimatsu | 17 Jul 2012 02:46

Re: [RFC PATCH v3 2/13] memory-hotplug : add physical memory hotplug code to acpi_memory_device_remove

Hi Wen,

2012/07/13 12:26, Wen Congyang wrote:
> At 07/09/2012 06:24 PM, Yasuaki Ishimatsu Wrote:
>> acpi_memory_device_remove() has been prepared to remove physical memory.
>> But, the function only frees acpi_memory_device currentlry.
>>
>> The patch adds following functions into acpi_memory_device_remove():
>>    - offline memory
>>    - remove physical memory (only return -EBUSY)
>>    - free acpi_memory_device
>>
>> CC: David Rientjes <rientjes <at> google.com>
>> CC: Jiang Liu <liuj97 <at> gmail.com>
>> CC: Len Brown <len.brown <at> intel.com>
>> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
>> CC: Paul Mackerras <paulus <at> samba.org>
>> CC: Christoph Lameter <cl <at> linux.com>
>> Cc: Minchan Kim <minchan.kim <at> gmail.com>
>> CC: Andrew Morton <akpm <at> linux-foundation.org>
>> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
>> CC: Wen Congyang <wency <at> cn.fujitsu.com>
>> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>
>>
>> ---
>>   drivers/acpi/acpi_memhotplug.c |   26 +++++++++++++++++++++++++-
>>   drivers/base/memory.c          |   39 +++++++++++++++++++++++++++++++++++++++
>>   include/linux/memory.h         |    5 +++++
>>   include/linux/memory_hotplug.h |    1 +
>>   mm/memory_hotplug.c            |    8 ++++++++

(Continue reading)

headers

Wen Congyang | 13 Jul 2012 05:26

Re: [RFC PATCH v3 2/13] memory-hotplug : add physical memory hotplug code to acpi_memory_device_remove

At 07/09/2012 06:24 PM, Yasuaki Ishimatsu Wrote:
> acpi_memory_device_remove() has been prepared to remove physical memory.
> But, the function only frees acpi_memory_device currentlry.
> 
> The patch adds following functions into acpi_memory_device_remove():
>   - offline memory
>   - remove physical memory (only return -EBUSY)
>   - free acpi_memory_device
> 
> CC: David Rientjes <rientjes <at> google.com>
> CC: Jiang Liu <liuj97 <at> gmail.com>
> CC: Len Brown <len.brown <at> intel.com>
> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
> CC: Paul Mackerras <paulus <at> samba.org>
> CC: Christoph Lameter <cl <at> linux.com>
> Cc: Minchan Kim <minchan.kim <at> gmail.com>
> CC: Andrew Morton <akpm <at> linux-foundation.org>
> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
> CC: Wen Congyang <wency <at> cn.fujitsu.com>
> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>
> 
> ---
>  drivers/acpi/acpi_memhotplug.c |   26 +++++++++++++++++++++++++-
>  drivers/base/memory.c          |   39 +++++++++++++++++++++++++++++++++++++++
>  include/linux/memory.h         |    5 +++++
>  include/linux/memory_hotplug.h |    1 +
>  mm/memory_hotplug.c            |    8 ++++++++
>  5 files changed, 78 insertions(+), 1 deletion(-)
> 
> Index: linux-3.5-rc6/drivers/acpi/acpi_memhotplug.c

(Continue reading)

headers

Wen Congyang | 13 Jul 2012 05:35

Re: [RFC PATCH v3 2/13] memory-hotplug : add physical memory hotplug code to acpi_memory_device_remove

At 07/09/2012 06:24 PM, Yasuaki Ishimatsu Wrote:
> acpi_memory_device_remove() has been prepared to remove physical memory.
> But, the function only frees acpi_memory_device currentlry.
> 
> The patch adds following functions into acpi_memory_device_remove():
>   - offline memory
>   - remove physical memory (only return -EBUSY)
>   - free acpi_memory_device
> 
> CC: David Rientjes <rientjes <at> google.com>
> CC: Jiang Liu <liuj97 <at> gmail.com>
> CC: Len Brown <len.brown <at> intel.com>
> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
> CC: Paul Mackerras <paulus <at> samba.org>
> CC: Christoph Lameter <cl <at> linux.com>
> Cc: Minchan Kim <minchan.kim <at> gmail.com>
> CC: Andrew Morton <akpm <at> linux-foundation.org>
> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
> CC: Wen Congyang <wency <at> cn.fujitsu.com>
> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>
> 
> ---
>  drivers/acpi/acpi_memhotplug.c |   26 +++++++++++++++++++++++++-
>  drivers/base/memory.c          |   39 +++++++++++++++++++++++++++++++++++++++
>  include/linux/memory.h         |    5 +++++
>  include/linux/memory_hotplug.h |    1 +
>  mm/memory_hotplug.c            |    8 ++++++++
>  5 files changed, 78 insertions(+), 1 deletion(-)
> 
> Index: linux-3.5-rc6/drivers/acpi/acpi_memhotplug.c

(Continue reading)

headers

Yasuaki Ishimatsu | 17 Jul 2012 03:44

Re: [RFC PATCH v3 2/13] memory-hotplug : add physical memory hotplug code to acpi_memory_device_remove

Hi Wen,

2012/07/13 12:35, Wen Congyang wrote:
> At 07/09/2012 06:24 PM, Yasuaki Ishimatsu Wrote:
>> acpi_memory_device_remove() has been prepared to remove physical memory.
>> But, the function only frees acpi_memory_device currentlry.
>>
>> The patch adds following functions into acpi_memory_device_remove():
>>    - offline memory
>>    - remove physical memory (only return -EBUSY)
>>    - free acpi_memory_device
>>
>> CC: David Rientjes <rientjes <at> google.com>
>> CC: Jiang Liu <liuj97 <at> gmail.com>
>> CC: Len Brown <len.brown <at> intel.com>
>> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
>> CC: Paul Mackerras <paulus <at> samba.org>
>> CC: Christoph Lameter <cl <at> linux.com>
>> Cc: Minchan Kim <minchan.kim <at> gmail.com>
>> CC: Andrew Morton <akpm <at> linux-foundation.org>
>> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
>> CC: Wen Congyang <wency <at> cn.fujitsu.com>
>> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>
>>
>> ---
>>   drivers/acpi/acpi_memhotplug.c |   26 +++++++++++++++++++++++++-
>>   drivers/base/memory.c          |   39 +++++++++++++++++++++++++++++++++++++++
>>   include/linux/memory.h         |    5 +++++
>>   include/linux/memory_hotplug.h |    1 +
>>   mm/memory_hotplug.c            |    8 ++++++++

(Continue reading)

headers

Yasuaki Ishimatsu | 17 Jul 2012 03:54

Re: [RFC PATCH v3 2/13] memory-hotplug : add physical memory hotplug code to acpi_memory_device_remove

Hi Wen,

2012/07/17 10:44, Yasuaki Ishimatsu wrote:
> Hi Wen,
> 
> 2012/07/13 12:35, Wen Congyang wrote:
>> At 07/09/2012 06:24 PM, Yasuaki Ishimatsu Wrote:
>>> acpi_memory_device_remove() has been prepared to remove physical memory.
>>> But, the function only frees acpi_memory_device currentlry.
>>>
>>> The patch adds following functions into acpi_memory_device_remove():
>>>     - offline memory
>>>     - remove physical memory (only return -EBUSY)
>>>     - free acpi_memory_device
>>>
>>> CC: David Rientjes <rientjes <at> google.com>
>>> CC: Jiang Liu <liuj97 <at> gmail.com>
>>> CC: Len Brown <len.brown <at> intel.com>
>>> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
>>> CC: Paul Mackerras <paulus <at> samba.org>
>>> CC: Christoph Lameter <cl <at> linux.com>
>>> Cc: Minchan Kim <minchan.kim <at> gmail.com>
>>> CC: Andrew Morton <akpm <at> linux-foundation.org>
>>> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
>>> CC: Wen Congyang <wency <at> cn.fujitsu.com>
>>> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>
>>>
>>> ---
>>>    drivers/acpi/acpi_memhotplug.c |   26 +++++++++++++++++++++++++-
>>>    drivers/base/memory.c          |   39 +++++++++++++++++++++++++++++++++++++++

(Continue reading)

headers

Wen Congyang | 17 Jul 2012 04:32

Re: [RFC PATCH v3 2/13] memory-hotplug : add physical memory hotplug code to acpi_memory_device_remove

At 07/17/2012 09:54 AM, Yasuaki Ishimatsu Wrote:
> Hi Wen,
> 
> 2012/07/17 10:44, Yasuaki Ishimatsu wrote:
>> Hi Wen,
>>
>> 2012/07/13 12:35, Wen Congyang wrote:
>>> At 07/09/2012 06:24 PM, Yasuaki Ishimatsu Wrote:
>>>> acpi_memory_device_remove() has been prepared to remove physical memory.
>>>> But, the function only frees acpi_memory_device currentlry.
>>>>
>>>> The patch adds following functions into acpi_memory_device_remove():
>>>>     - offline memory
>>>>     - remove physical memory (only return -EBUSY)
>>>>     - free acpi_memory_device
>>>>
>>>> CC: David Rientjes <rientjes <at> google.com>
>>>> CC: Jiang Liu <liuj97 <at> gmail.com>
>>>> CC: Len Brown <len.brown <at> intel.com>
>>>> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
>>>> CC: Paul Mackerras <paulus <at> samba.org>
>>>> CC: Christoph Lameter <cl <at> linux.com>
>>>> Cc: Minchan Kim <minchan.kim <at> gmail.com>
>>>> CC: Andrew Morton <akpm <at> linux-foundation.org>
>>>> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
>>>> CC: Wen Congyang <wency <at> cn.fujitsu.com>
>>>> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>
>>>>
>>>> ---
>>>>    drivers/acpi/acpi_memhotplug.c |   26 +++++++++++++++++++++++++-

(Continue reading)

headers

Yasuaki Ishimatsu | 17 Jul 2012 05:08

Re: [RFC PATCH v3 2/13] memory-hotplug : add physical memory hotplug code to acpi_memory_device_remove

Hi Wen,

2012/07/17 11:32, Wen Congyang wrote:
> At 07/17/2012 09:54 AM, Yasuaki Ishimatsu Wrote:
>> Hi Wen,
>>
>> 2012/07/17 10:44, Yasuaki Ishimatsu wrote:
>>> Hi Wen,
>>>
>>> 2012/07/13 12:35, Wen Congyang wrote:
>>>> At 07/09/2012 06:24 PM, Yasuaki Ishimatsu Wrote:
>>>>> acpi_memory_device_remove() has been prepared to remove physical memory.
>>>>> But, the function only frees acpi_memory_device currentlry.
>>>>>
>>>>> The patch adds following functions into acpi_memory_device_remove():
>>>>>      - offline memory
>>>>>      - remove physical memory (only return -EBUSY)
>>>>>      - free acpi_memory_device
>>>>>
>>>>> CC: David Rientjes <rientjes <at> google.com>
>>>>> CC: Jiang Liu <liuj97 <at> gmail.com>
>>>>> CC: Len Brown <len.brown <at> intel.com>
>>>>> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
>>>>> CC: Paul Mackerras <paulus <at> samba.org>
>>>>> CC: Christoph Lameter <cl <at> linux.com>
>>>>> Cc: Minchan Kim <minchan.kim <at> gmail.com>
>>>>> CC: Andrew Morton <akpm <at> linux-foundation.org>
>>>>> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
>>>>> CC: Wen Congyang <wency <at> cn.fujitsu.com>
>>>>> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>

(Continue reading)

headers

Wen Congyang | 17 Jul 2012 05:32

Re: [RFC PATCH v3 2/13] memory-hotplug : add physical memory hotplug code to acpi_memory_device_remove

At 07/17/2012 11:08 AM, Yasuaki Ishimatsu Wrote:
> Hi Wen,
> 
> 2012/07/17 11:32, Wen Congyang wrote:
>> At 07/17/2012 09:54 AM, Yasuaki Ishimatsu Wrote:
>>> Hi Wen,
>>>
>>> 2012/07/17 10:44, Yasuaki Ishimatsu wrote:
>>>> Hi Wen,
>>>>
>>>> 2012/07/13 12:35, Wen Congyang wrote:
>>>>> At 07/09/2012 06:24 PM, Yasuaki Ishimatsu Wrote:
>>>>>> acpi_memory_device_remove() has been prepared to remove physical memory.
>>>>>> But, the function only frees acpi_memory_device currentlry.
>>>>>>
>>>>>> The patch adds following functions into acpi_memory_device_remove():
>>>>>>      - offline memory
>>>>>>      - remove physical memory (only return -EBUSY)
>>>>>>      - free acpi_memory_device
>>>>>>
>>>>>> CC: David Rientjes <rientjes <at> google.com>
>>>>>> CC: Jiang Liu <liuj97 <at> gmail.com>
>>>>>> CC: Len Brown <len.brown <at> intel.com>
>>>>>> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
>>>>>> CC: Paul Mackerras <paulus <at> samba.org>
>>>>>> CC: Christoph Lameter <cl <at> linux.com>
>>>>>> Cc: Minchan Kim <minchan.kim <at> gmail.com>
>>>>>> CC: Andrew Morton <akpm <at> linux-foundation.org>
>>>>>> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
>>>>>> CC: Wen Congyang <wency <at> cn.fujitsu.com>

(Continue reading)

headers

Yasuaki Ishimatsu | 17 Jul 2012 06:51

Re: [RFC PATCH v3 2/13] memory-hotplug : add physical memory hotplug code to acpi_memory_device_remove

Hi Wen,

2012/07/17 12:32, Wen Congyang wrote:
> At 07/17/2012 11:08 AM, Yasuaki Ishimatsu Wrote:
>> Hi Wen,
>>
>> 2012/07/17 11:32, Wen Congyang wrote:
>>> At 07/17/2012 09:54 AM, Yasuaki Ishimatsu Wrote:
>>>> Hi Wen,
>>>>
>>>> 2012/07/17 10:44, Yasuaki Ishimatsu wrote:
>>>>> Hi Wen,
>>>>>
>>>>> 2012/07/13 12:35, Wen Congyang wrote:
>>>>>> At 07/09/2012 06:24 PM, Yasuaki Ishimatsu Wrote:
>>>>>>> acpi_memory_device_remove() has been prepared to remove physical memory.
>>>>>>> But, the function only frees acpi_memory_device currentlry.
>>>>>>>
>>>>>>> The patch adds following functions into acpi_memory_device_remove():
>>>>>>>       - offline memory
>>>>>>>       - remove physical memory (only return -EBUSY)
>>>>>>>       - free acpi_memory_device
>>>>>>>
>>>>>>> CC: David Rientjes <rientjes <at> google.com>
>>>>>>> CC: Jiang Liu <liuj97 <at> gmail.com>
>>>>>>> CC: Len Brown <len.brown <at> intel.com>
>>>>>>> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
>>>>>>> CC: Paul Mackerras <paulus <at> samba.org>
>>>>>>> CC: Christoph Lameter <cl <at> linux.com>
>>>>>>> Cc: Minchan Kim <minchan.kim <at> gmail.com>

(Continue reading)

headers

Wen Congyang | 17 Jul 2012 07:17

Re: [RFC PATCH v3 2/13] memory-hotplug : add physical memory hotplug code to acpi_memory_device_remove

At 07/17/2012 12:51 PM, Yasuaki Ishimatsu Wrote:
> Hi Wen,
> 
> 2012/07/17 12:32, Wen Congyang wrote:
>> At 07/17/2012 11:08 AM, Yasuaki Ishimatsu Wrote:
>>> Hi Wen,
>>>
>>> 2012/07/17 11:32, Wen Congyang wrote:
>>>> At 07/17/2012 09:54 AM, Yasuaki Ishimatsu Wrote:
>>>>> Hi Wen,
>>>>>
>>>>> 2012/07/17 10:44, Yasuaki Ishimatsu wrote:
>>>>>> Hi Wen,
>>>>>>
>>>>>> 2012/07/13 12:35, Wen Congyang wrote:
>>>>>>> At 07/09/2012 06:24 PM, Yasuaki Ishimatsu Wrote:
>>>>>>>> acpi_memory_device_remove() has been prepared to remove physical memory.
>>>>>>>> But, the function only frees acpi_memory_device currentlry.
>>>>>>>>
>>>>>>>> The patch adds following functions into acpi_memory_device_remove():
>>>>>>>>       - offline memory
>>>>>>>>       - remove physical memory (only return -EBUSY)
>>>>>>>>       - free acpi_memory_device
>>>>>>>>
>>>>>>>> CC: David Rientjes <rientjes <at> google.com>
>>>>>>>> CC: Jiang Liu <liuj97 <at> gmail.com>
>>>>>>>> CC: Len Brown <len.brown <at> intel.com>
>>>>>>>> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
>>>>>>>> CC: Paul Mackerras <paulus <at> samba.org>
>>>>>>>> CC: Christoph Lameter <cl <at> linux.com>

(Continue reading)

headers

Yasuaki Ishimatsu | 17 Jul 2012 07:19

Re: [RFC PATCH v3 2/13] memory-hotplug : add physical memory hotplug code to acpi_memory_device_remove

Hi Wen,

2012/07/17 14:17, Wen Congyang wrote:
> At 07/17/2012 12:51 PM, Yasuaki Ishimatsu Wrote:
>> Hi Wen,
>>
>> 2012/07/17 12:32, Wen Congyang wrote:
>>> At 07/17/2012 11:08 AM, Yasuaki Ishimatsu Wrote:
>>>> Hi Wen,
>>>>
>>>> 2012/07/17 11:32, Wen Congyang wrote:
>>>>> At 07/17/2012 09:54 AM, Yasuaki Ishimatsu Wrote:
>>>>>> Hi Wen,
>>>>>>
>>>>>> 2012/07/17 10:44, Yasuaki Ishimatsu wrote:
>>>>>>> Hi Wen,
>>>>>>>
>>>>>>> 2012/07/13 12:35, Wen Congyang wrote:
>>>>>>>> At 07/09/2012 06:24 PM, Yasuaki Ishimatsu Wrote:
>>>>>>>>> acpi_memory_device_remove() has been prepared to remove physical memory.
>>>>>>>>> But, the function only frees acpi_memory_device currentlry.
>>>>>>>>>
>>>>>>>>> The patch adds following functions into acpi_memory_device_remove():
>>>>>>>>>        - offline memory
>>>>>>>>>        - remove physical memory (only return -EBUSY)
>>>>>>>>>        - free acpi_memory_device
>>>>>>>>>
>>>>>>>>> CC: David Rientjes <rientjes <at> google.com>
>>>>>>>>> CC: Jiang Liu <liuj97 <at> gmail.com>
>>>>>>>>> CC: Len Brown <len.brown <at> intel.com>

(Continue reading)

headers

Yasuaki Ishimatsu | 17 Jul 2012 07:19

Re: [RFC PATCH v3 2/13] memory-hotplug : add physical memory hotplug code to acpi_memory_device_remove

Hi Wen,

2012/07/17 14:17, Wen Congyang wrote:
> At 07/17/2012 12:51 PM, Yasuaki Ishimatsu Wrote:
>> Hi Wen,
>>
>> 2012/07/17 12:32, Wen Congyang wrote:
>>> At 07/17/2012 11:08 AM, Yasuaki Ishimatsu Wrote:
>>>> Hi Wen,
>>>>
>>>> 2012/07/17 11:32, Wen Congyang wrote:
>>>>> At 07/17/2012 09:54 AM, Yasuaki Ishimatsu Wrote:
>>>>>> Hi Wen,
>>>>>>
>>>>>> 2012/07/17 10:44, Yasuaki Ishimatsu wrote:
>>>>>>> Hi Wen,
>>>>>>>
>>>>>>> 2012/07/13 12:35, Wen Congyang wrote:
>>>>>>>> At 07/09/2012 06:24 PM, Yasuaki Ishimatsu Wrote:
>>>>>>>>> acpi_memory_device_remove() has been prepared to remove physical memory.
>>>>>>>>> But, the function only frees acpi_memory_device currentlry.
>>>>>>>>>
>>>>>>>>> The patch adds following functions into acpi_memory_device_remove():
>>>>>>>>>        - offline memory
>>>>>>>>>        - remove physical memory (only return -EBUSY)
>>>>>>>>>        - free acpi_memory_device
>>>>>>>>>
>>>>>>>>> CC: David Rientjes <rientjes <at> google.com>
>>>>>>>>> CC: Jiang Liu <liuj97 <at> gmail.com>
>>>>>>>>> CC: Len Brown <len.brown <at> intel.com>

(Continue reading)

headers

Wen Congyang | 17 Jul 2012 07:17

Re: [RFC PATCH v3 2/13] memory-hotplug : add physical memory hotplug code to acpi_memory_device_remove

At 07/17/2012 12:51 PM, Yasuaki Ishimatsu Wrote:
> Hi Wen,
> 
> 2012/07/17 12:32, Wen Congyang wrote:
>> At 07/17/2012 11:08 AM, Yasuaki Ishimatsu Wrote:
>>> Hi Wen,
>>>
>>> 2012/07/17 11:32, Wen Congyang wrote:
>>>> At 07/17/2012 09:54 AM, Yasuaki Ishimatsu Wrote:
>>>>> Hi Wen,
>>>>>
>>>>> 2012/07/17 10:44, Yasuaki Ishimatsu wrote:
>>>>>> Hi Wen,
>>>>>>
>>>>>> 2012/07/13 12:35, Wen Congyang wrote:
>>>>>>> At 07/09/2012 06:24 PM, Yasuaki Ishimatsu Wrote:
>>>>>>>> acpi_memory_device_remove() has been prepared to remove physical memory.
>>>>>>>> But, the function only frees acpi_memory_device currentlry.
>>>>>>>>
>>>>>>>> The patch adds following functions into acpi_memory_device_remove():
>>>>>>>>       - offline memory
>>>>>>>>       - remove physical memory (only return -EBUSY)
>>>>>>>>       - free acpi_memory_device
>>>>>>>>
>>>>>>>> CC: David Rientjes <rientjes <at> google.com>
>>>>>>>> CC: Jiang Liu <liuj97 <at> gmail.com>
>>>>>>>> CC: Len Brown <len.brown <at> intel.com>
>>>>>>>> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
>>>>>>>> CC: Paul Mackerras <paulus <at> samba.org>
>>>>>>>> CC: Christoph Lameter <cl <at> linux.com>

(Continue reading)

headers

Yasuaki Ishimatsu | 17 Jul 2012 06:51

Re: [RFC PATCH v3 2/13] memory-hotplug : add physical memory hotplug code to acpi_memory_device_remove

Hi Wen,

2012/07/17 12:32, Wen Congyang wrote:
> At 07/17/2012 11:08 AM, Yasuaki Ishimatsu Wrote:
>> Hi Wen,
>>
>> 2012/07/17 11:32, Wen Congyang wrote:
>>> At 07/17/2012 09:54 AM, Yasuaki Ishimatsu Wrote:
>>>> Hi Wen,
>>>>
>>>> 2012/07/17 10:44, Yasuaki Ishimatsu wrote:
>>>>> Hi Wen,
>>>>>
>>>>> 2012/07/13 12:35, Wen Congyang wrote:
>>>>>> At 07/09/2012 06:24 PM, Yasuaki Ishimatsu Wrote:
>>>>>>> acpi_memory_device_remove() has been prepared to remove physical memory.
>>>>>>> But, the function only frees acpi_memory_device currentlry.
>>>>>>>
>>>>>>> The patch adds following functions into acpi_memory_device_remove():
>>>>>>>       - offline memory
>>>>>>>       - remove physical memory (only return -EBUSY)
>>>>>>>       - free acpi_memory_device
>>>>>>>
>>>>>>> CC: David Rientjes <rientjes <at> google.com>
>>>>>>> CC: Jiang Liu <liuj97 <at> gmail.com>
>>>>>>> CC: Len Brown <len.brown <at> intel.com>
>>>>>>> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
>>>>>>> CC: Paul Mackerras <paulus <at> samba.org>
>>>>>>> CC: Christoph Lameter <cl <at> linux.com>
>>>>>>> Cc: Minchan Kim <minchan.kim <at> gmail.com>

(Continue reading)

headers

Wen Congyang | 17 Jul 2012 05:32

Re: [RFC PATCH v3 2/13] memory-hotplug : add physical memory hotplug code to acpi_memory_device_remove

At 07/17/2012 11:08 AM, Yasuaki Ishimatsu Wrote:
> Hi Wen,
> 
> 2012/07/17 11:32, Wen Congyang wrote:
>> At 07/17/2012 09:54 AM, Yasuaki Ishimatsu Wrote:
>>> Hi Wen,
>>>
>>> 2012/07/17 10:44, Yasuaki Ishimatsu wrote:
>>>> Hi Wen,
>>>>
>>>> 2012/07/13 12:35, Wen Congyang wrote:
>>>>> At 07/09/2012 06:24 PM, Yasuaki Ishimatsu Wrote:
>>>>>> acpi_memory_device_remove() has been prepared to remove physical memory.
>>>>>> But, the function only frees acpi_memory_device currentlry.
>>>>>>
>>>>>> The patch adds following functions into acpi_memory_device_remove():
>>>>>>      - offline memory
>>>>>>      - remove physical memory (only return -EBUSY)
>>>>>>      - free acpi_memory_device
>>>>>>
>>>>>> CC: David Rientjes <rientjes <at> google.com>
>>>>>> CC: Jiang Liu <liuj97 <at> gmail.com>
>>>>>> CC: Len Brown <len.brown <at> intel.com>
>>>>>> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
>>>>>> CC: Paul Mackerras <paulus <at> samba.org>
>>>>>> CC: Christoph Lameter <cl <at> linux.com>
>>>>>> Cc: Minchan Kim <minchan.kim <at> gmail.com>
>>>>>> CC: Andrew Morton <akpm <at> linux-foundation.org>
>>>>>> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
>>>>>> CC: Wen Congyang <wency <at> cn.fujitsu.com>

(Continue reading)

headers

Yasuaki Ishimatsu | 17 Jul 2012 05:08

Re: [RFC PATCH v3 2/13] memory-hotplug : add physical memory hotplug code to acpi_memory_device_remove

Hi Wen,

2012/07/17 11:32, Wen Congyang wrote:
> At 07/17/2012 09:54 AM, Yasuaki Ishimatsu Wrote:
>> Hi Wen,
>>
>> 2012/07/17 10:44, Yasuaki Ishimatsu wrote:
>>> Hi Wen,
>>>
>>> 2012/07/13 12:35, Wen Congyang wrote:
>>>> At 07/09/2012 06:24 PM, Yasuaki Ishimatsu Wrote:
>>>>> acpi_memory_device_remove() has been prepared to remove physical memory.
>>>>> But, the function only frees acpi_memory_device currentlry.
>>>>>
>>>>> The patch adds following functions into acpi_memory_device_remove():
>>>>>      - offline memory
>>>>>      - remove physical memory (only return -EBUSY)
>>>>>      - free acpi_memory_device
>>>>>
>>>>> CC: David Rientjes <rientjes <at> google.com>
>>>>> CC: Jiang Liu <liuj97 <at> gmail.com>
>>>>> CC: Len Brown <len.brown <at> intel.com>
>>>>> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
>>>>> CC: Paul Mackerras <paulus <at> samba.org>
>>>>> CC: Christoph Lameter <cl <at> linux.com>
>>>>> Cc: Minchan Kim <minchan.kim <at> gmail.com>
>>>>> CC: Andrew Morton <akpm <at> linux-foundation.org>
>>>>> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
>>>>> CC: Wen Congyang <wency <at> cn.fujitsu.com>
>>>>> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>

(Continue reading)

headers

Wen Congyang | 17 Jul 2012 04:32

Re: [RFC PATCH v3 2/13] memory-hotplug : add physical memory hotplug code to acpi_memory_device_remove

At 07/17/2012 09:54 AM, Yasuaki Ishimatsu Wrote:
> Hi Wen,
> 
> 2012/07/17 10:44, Yasuaki Ishimatsu wrote:
>> Hi Wen,
>>
>> 2012/07/13 12:35, Wen Congyang wrote:
>>> At 07/09/2012 06:24 PM, Yasuaki Ishimatsu Wrote:
>>>> acpi_memory_device_remove() has been prepared to remove physical memory.
>>>> But, the function only frees acpi_memory_device currentlry.
>>>>
>>>> The patch adds following functions into acpi_memory_device_remove():
>>>>     - offline memory
>>>>     - remove physical memory (only return -EBUSY)
>>>>     - free acpi_memory_device
>>>>
>>>> CC: David Rientjes <rientjes <at> google.com>
>>>> CC: Jiang Liu <liuj97 <at> gmail.com>
>>>> CC: Len Brown <len.brown <at> intel.com>
>>>> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
>>>> CC: Paul Mackerras <paulus <at> samba.org>
>>>> CC: Christoph Lameter <cl <at> linux.com>
>>>> Cc: Minchan Kim <minchan.kim <at> gmail.com>
>>>> CC: Andrew Morton <akpm <at> linux-foundation.org>
>>>> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
>>>> CC: Wen Congyang <wency <at> cn.fujitsu.com>
>>>> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>
>>>>
>>>> ---
>>>>    drivers/acpi/acpi_memhotplug.c |   26 +++++++++++++++++++++++++-

(Continue reading)

headers

Yasuaki Ishimatsu | 17 Jul 2012 03:54

Re: [RFC PATCH v3 2/13] memory-hotplug : add physical memory hotplug code to acpi_memory_device_remove

Hi Wen,

2012/07/17 10:44, Yasuaki Ishimatsu wrote:
> Hi Wen,
> 
> 2012/07/13 12:35, Wen Congyang wrote:
>> At 07/09/2012 06:24 PM, Yasuaki Ishimatsu Wrote:
>>> acpi_memory_device_remove() has been prepared to remove physical memory.
>>> But, the function only frees acpi_memory_device currentlry.
>>>
>>> The patch adds following functions into acpi_memory_device_remove():
>>>     - offline memory
>>>     - remove physical memory (only return -EBUSY)
>>>     - free acpi_memory_device
>>>
>>> CC: David Rientjes <rientjes <at> google.com>
>>> CC: Jiang Liu <liuj97 <at> gmail.com>
>>> CC: Len Brown <len.brown <at> intel.com>
>>> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
>>> CC: Paul Mackerras <paulus <at> samba.org>
>>> CC: Christoph Lameter <cl <at> linux.com>
>>> Cc: Minchan Kim <minchan.kim <at> gmail.com>
>>> CC: Andrew Morton <akpm <at> linux-foundation.org>
>>> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
>>> CC: Wen Congyang <wency <at> cn.fujitsu.com>
>>> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>
>>>
>>> ---
>>>    drivers/acpi/acpi_memhotplug.c |   26 +++++++++++++++++++++++++-
>>>    drivers/base/memory.c          |   39 +++++++++++++++++++++++++++++++++++++++

(Continue reading)

headers

Yasuaki Ishimatsu | 17 Jul 2012 03:44

Re: [RFC PATCH v3 2/13] memory-hotplug : add physical memory hotplug code to acpi_memory_device_remove

Hi Wen,

2012/07/13 12:35, Wen Congyang wrote:
> At 07/09/2012 06:24 PM, Yasuaki Ishimatsu Wrote:
>> acpi_memory_device_remove() has been prepared to remove physical memory.
>> But, the function only frees acpi_memory_device currentlry.
>>
>> The patch adds following functions into acpi_memory_device_remove():
>>    - offline memory
>>    - remove physical memory (only return -EBUSY)
>>    - free acpi_memory_device
>>
>> CC: David Rientjes <rientjes <at> google.com>
>> CC: Jiang Liu <liuj97 <at> gmail.com>
>> CC: Len Brown <len.brown <at> intel.com>
>> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
>> CC: Paul Mackerras <paulus <at> samba.org>
>> CC: Christoph Lameter <cl <at> linux.com>
>> Cc: Minchan Kim <minchan.kim <at> gmail.com>
>> CC: Andrew Morton <akpm <at> linux-foundation.org>
>> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
>> CC: Wen Congyang <wency <at> cn.fujitsu.com>
>> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>
>>
>> ---
>>   drivers/acpi/acpi_memhotplug.c |   26 +++++++++++++++++++++++++-
>>   drivers/base/memory.c          |   39 +++++++++++++++++++++++++++++++++++++++
>>   include/linux/memory.h         |    5 +++++
>>   include/linux/memory_hotplug.h |    1 +
>>   mm/memory_hotplug.c            |    8 ++++++++

(Continue reading)

headers

Wen Congyang | 13 Jul 2012 05:35

Re: [RFC PATCH v3 2/13] memory-hotplug : add physical memory hotplug code to acpi_memory_device_remove

At 07/09/2012 06:24 PM, Yasuaki Ishimatsu Wrote:
> acpi_memory_device_remove() has been prepared to remove physical memory.
> But, the function only frees acpi_memory_device currentlry.
> 
> The patch adds following functions into acpi_memory_device_remove():
>   - offline memory
>   - remove physical memory (only return -EBUSY)
>   - free acpi_memory_device
> 
> CC: David Rientjes <rientjes <at> google.com>
> CC: Jiang Liu <liuj97 <at> gmail.com>
> CC: Len Brown <len.brown <at> intel.com>
> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
> CC: Paul Mackerras <paulus <at> samba.org>
> CC: Christoph Lameter <cl <at> linux.com>
> Cc: Minchan Kim <minchan.kim <at> gmail.com>
> CC: Andrew Morton <akpm <at> linux-foundation.org>
> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
> CC: Wen Congyang <wency <at> cn.fujitsu.com>
> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>
> 
> ---
>  drivers/acpi/acpi_memhotplug.c |   26 +++++++++++++++++++++++++-
>  drivers/base/memory.c          |   39 +++++++++++++++++++++++++++++++++++++++
>  include/linux/memory.h         |    5 +++++
>  include/linux/memory_hotplug.h |    1 +
>  mm/memory_hotplug.c            |    8 ++++++++
>  5 files changed, 78 insertions(+), 1 deletion(-)
> 
> Index: linux-3.5-rc6/drivers/acpi/acpi_memhotplug.c

(Continue reading)

headers

Wen Congyang | 13 Jul 2012 12:40

Re: [RFC PATCH v3 2/13] memory-hotplug : add physical memory hotplug code to acpi_memory_device_remove

At 07/09/2012 06:24 PM, Yasuaki Ishimatsu Wrote:
> acpi_memory_device_remove() has been prepared to remove physical memory.
> But, the function only frees acpi_memory_device currentlry.
> 
> The patch adds following functions into acpi_memory_device_remove():
>   - offline memory
>   - remove physical memory (only return -EBUSY)
>   - free acpi_memory_device
> 
> CC: David Rientjes <rientjes <at> google.com>
> CC: Jiang Liu <liuj97 <at> gmail.com>
> CC: Len Brown <len.brown <at> intel.com>
> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
> CC: Paul Mackerras <paulus <at> samba.org>
> CC: Christoph Lameter <cl <at> linux.com>
> Cc: Minchan Kim <minchan.kim <at> gmail.com>
> CC: Andrew Morton <akpm <at> linux-foundation.org>
> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
> CC: Wen Congyang <wency <at> cn.fujitsu.com>
> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>
> 
> ---
>  drivers/acpi/acpi_memhotplug.c |   26 +++++++++++++++++++++++++-
>  drivers/base/memory.c          |   39 +++++++++++++++++++++++++++++++++++++++
>  include/linux/memory.h         |    5 +++++
>  include/linux/memory_hotplug.h |    1 +
>  mm/memory_hotplug.c            |    8 ++++++++
>  5 files changed, 78 insertions(+), 1 deletion(-)
> 
> Index: linux-3.5-rc6/drivers/acpi/acpi_memhotplug.c

(Continue reading)

headers

Yasuaki Ishimatsu | 17 Jul 2012 03:10

Re: [RFC PATCH v3 2/13] memory-hotplug : add physical memory hotplug code to acpi_memory_device_remove

Hi Wen,

2012/07/13 19:40, Wen Congyang wrote:
> At 07/09/2012 06:24 PM, Yasuaki Ishimatsu Wrote:
>> acpi_memory_device_remove() has been prepared to remove physical memory.
>> But, the function only frees acpi_memory_device currentlry.
>>
>> The patch adds following functions into acpi_memory_device_remove():
>>    - offline memory
>>    - remove physical memory (only return -EBUSY)
>>    - free acpi_memory_device
>>
>> CC: David Rientjes <rientjes <at> google.com>
>> CC: Jiang Liu <liuj97 <at> gmail.com>
>> CC: Len Brown <len.brown <at> intel.com>
>> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
>> CC: Paul Mackerras <paulus <at> samba.org>
>> CC: Christoph Lameter <cl <at> linux.com>
>> Cc: Minchan Kim <minchan.kim <at> gmail.com>
>> CC: Andrew Morton <akpm <at> linux-foundation.org>
>> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
>> CC: Wen Congyang <wency <at> cn.fujitsu.com>
>> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>
>>
>> ---
>>   drivers/acpi/acpi_memhotplug.c |   26 +++++++++++++++++++++++++-
>>   drivers/base/memory.c          |   39 +++++++++++++++++++++++++++++++++++++++
>>   include/linux/memory.h         |    5 +++++
>>   include/linux/memory_hotplug.h |    1 +
>>   mm/memory_hotplug.c            |    8 ++++++++

(Continue reading)

headers

Yasuaki Ishimatsu | 17 Jul 2012 03:10

Re: [RFC PATCH v3 2/13] memory-hotplug : add physical memory hotplug code to acpi_memory_device_remove

Hi Wen,

2012/07/13 19:40, Wen Congyang wrote:
> At 07/09/2012 06:24 PM, Yasuaki Ishimatsu Wrote:
>> acpi_memory_device_remove() has been prepared to remove physical memory.
>> But, the function only frees acpi_memory_device currentlry.
>>
>> The patch adds following functions into acpi_memory_device_remove():
>>    - offline memory
>>    - remove physical memory (only return -EBUSY)
>>    - free acpi_memory_device
>>
>> CC: David Rientjes <rientjes <at> google.com>
>> CC: Jiang Liu <liuj97 <at> gmail.com>
>> CC: Len Brown <len.brown <at> intel.com>
>> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
>> CC: Paul Mackerras <paulus <at> samba.org>
>> CC: Christoph Lameter <cl <at> linux.com>
>> Cc: Minchan Kim <minchan.kim <at> gmail.com>
>> CC: Andrew Morton <akpm <at> linux-foundation.org>
>> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
>> CC: Wen Congyang <wency <at> cn.fujitsu.com>
>> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>
>>
>> ---
>>   drivers/acpi/acpi_memhotplug.c |   26 +++++++++++++++++++++++++-
>>   drivers/base/memory.c          |   39 +++++++++++++++++++++++++++++++++++++++
>>   include/linux/memory.h         |    5 +++++
>>   include/linux/memory_hotplug.h |    1 +
>>   mm/memory_hotplug.c            |    8 ++++++++

(Continue reading)

headers

Wen Congyang | 13 Jul 2012 12:40

Re: [RFC PATCH v3 2/13] memory-hotplug : add physical memory hotplug code to acpi_memory_device_remove

At 07/09/2012 06:24 PM, Yasuaki Ishimatsu Wrote:
> acpi_memory_device_remove() has been prepared to remove physical memory.
> But, the function only frees acpi_memory_device currentlry.
> 
> The patch adds following functions into acpi_memory_device_remove():
>   - offline memory
>   - remove physical memory (only return -EBUSY)
>   - free acpi_memory_device
> 
> CC: David Rientjes <rientjes <at> google.com>
> CC: Jiang Liu <liuj97 <at> gmail.com>
> CC: Len Brown <len.brown <at> intel.com>
> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
> CC: Paul Mackerras <paulus <at> samba.org>
> CC: Christoph Lameter <cl <at> linux.com>
> Cc: Minchan Kim <minchan.kim <at> gmail.com>
> CC: Andrew Morton <akpm <at> linux-foundation.org>
> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
> CC: Wen Congyang <wency <at> cn.fujitsu.com>
> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>
> 
> ---
>  drivers/acpi/acpi_memhotplug.c |   26 +++++++++++++++++++++++++-
>  drivers/base/memory.c          |   39 +++++++++++++++++++++++++++++++++++++++
>  include/linux/memory.h         |    5 +++++
>  include/linux/memory_hotplug.h |    1 +
>  mm/memory_hotplug.c            |    8 ++++++++
>  5 files changed, 78 insertions(+), 1 deletion(-)
> 
> Index: linux-3.5-rc6/drivers/acpi/acpi_memhotplug.c

(Continue reading)

headers

Yasuaki Ishimatsu | 9 Jul 2012 12:24

[RFC PATCH v3 2/13] memory-hotplug : add physical memory hotplug code to acpi_memory_device_remove

acpi_memory_device_remove() has been prepared to remove physical memory.
But, the function only frees acpi_memory_device currentlry.

The patch adds following functions into acpi_memory_device_remove():
  - offline memory
  - remove physical memory (only return -EBUSY)
  - free acpi_memory_device

CC: David Rientjes <rientjes <at> google.com>
CC: Jiang Liu <liuj97 <at> gmail.com>
CC: Len Brown <len.brown <at> intel.com>
CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
CC: Paul Mackerras <paulus <at> samba.org>
CC: Christoph Lameter <cl <at> linux.com>
Cc: Minchan Kim <minchan.kim <at> gmail.com>
CC: Andrew Morton <akpm <at> linux-foundation.org>
CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
CC: Wen Congyang <wency <at> cn.fujitsu.com>
Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>

---
 drivers/acpi/acpi_memhotplug.c |   26 +++++++++++++++++++++++++-
 drivers/base/memory.c          |   39 +++++++++++++++++++++++++++++++++++++++
 include/linux/memory.h         |    5 +++++
 include/linux/memory_hotplug.h |    1 +
 mm/memory_hotplug.c            |    8 ++++++++
 5 files changed, 78 insertions(+), 1 deletion(-)

Index: linux-3.5-rc6/drivers/acpi/acpi_memhotplug.c
===================================================================

(Continue reading)

headers

Yasuaki Ishimatsu | 9 Jul 2012 12:25

[RFC PATCH v3 3/13] memory-hotplug : unify argument of firmware_map_add_early/hotplug

There are two ways to create /sys/firmware/memmap/X sysfs:

  - firmware_map_add_early
    When the system starts, it is calledd from e820_reserve_resources()
  - firmware_map_add_hotplug
    When the memory is hot plugged, it is called from add_memory()

But these functions are called without unifying value of end argument as below:

  - end argument of firmware_map_add_early()   : start + size - 1
  - end argument of firmware_map_add_hogplug() : start + size

The patch unifies them to "start + size - 1".

CC: David Rientjes <rientjes <at> google.com>
CC: Jiang Liu <liuj97 <at> gmail.com>
CC: Len Brown <len.brown <at> intel.com>
CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
CC: Paul Mackerras <paulus <at> samba.org>
CC: Christoph Lameter <cl <at> linux.com>
Cc: Minchan Kim <minchan.kim <at> gmail.com>
CC: Andrew Morton <akpm <at> linux-foundation.org>
CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
CC: Wen Congyang <wency <at> cn.fujitsu.com>
Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>

---
 mm/memory_hotplug.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(Continue reading)

headers

Dave Hansen | 11 Jul 2012 17:30

Re: [RFC PATCH v3 3/13] memory-hotplug : unify argument of firmware_map_add_early/hotplug

On 07/09/2012 03:25 AM, Yasuaki Ishimatsu wrote:
>  <at>  <at>  -642,7 +642,7  <at>  <at>  int __ref add_memory(int nid, u64 start,
>  	}
> 
>  	/* create new memmap entry */
> -	firmware_map_add_hotplug(start, start + size, "System RAM");
> +	firmware_map_add_hotplug(start, start + size - 1, "System RAM");

I know the firmware_map_*() calls use inclusive end addresses
internally, but do we really need to expose them?  Both of the callers
you mentioned do:

	firmware_map_add_hotplug(start, start + size - 1, "System RAM");

or

                firmware_map_add_early(entry->addr,
                        entry->addr + entry->size - 1,
                        e820_type_to_string(entry->type));

So it seems a _bit_ silly to keep all of the callers doing this size-1
thing.  I also noted that the new caller that you added does the same
thing.  Could we just change the external calling convention to be
exclusive?

BTW, this patch should probably be first in your series.  It's a real
bugfix.

--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in

(Continue reading)

headers

Yasuaki Ishimatsu | 12 Jul 2012 06:52

Re: [RFC PATCH v3 3/13] memory-hotplug : unify argument of firmware_map_add_early/hotplug

Hi Dave,

2012/07/12 0:30, Dave Hansen wrote:
> On 07/09/2012 03:25 AM, Yasuaki Ishimatsu wrote:
>>  <at>  <at>  -642,7 +642,7  <at>  <at>  int __ref add_memory(int nid, u64 start,
>>   	}
>>
>>   	/* create new memmap entry */
>> -	firmware_map_add_hotplug(start, start + size, "System RAM");
>> +	firmware_map_add_hotplug(start, start + size - 1, "System RAM");
> 
> I know the firmware_map_*() calls use inclusive end addresses
> internally, but do we really need to expose them?  Both of the callers
> you mentioned do:
> 
> 	firmware_map_add_hotplug(start, start + size - 1, "System RAM");
> 
> or
> 
>                  firmware_map_add_early(entry->addr,
>                          entry->addr + entry->size - 1,
>                          e820_type_to_string(entry->type));
> 
> So it seems a _bit_ silly to keep all of the callers doing this size-1
> thing.  I also noted that the new caller that you added does the same
> thing.  Could we just change the external calling convention to be
> exclusive?

Thank you for your comment.

(Continue reading)

headers

Dave Hansen | 12 Jul 2012 15:40

Re: [RFC PATCH v3 3/13] memory-hotplug : unify argument of firmware_map_add_early/hotplug

On 07/11/2012 09:52 PM, Yasuaki Ishimatsu wrote:
> Does the following patch include your comment? If O.K., I will separate
> the patch from the series and send it for bug fix.

Looks sane to me.  It does now mean that the calling conventions for
some of the other firmware_map*() functions are different, but I think
that's OK since they're only used internally to memmap.c.

--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

headers

Yasuaki Ishimatsu | 13 Jul 2012 06:34

Re: [RFC PATCH v3 3/13] memory-hotplug : unify argument of firmware_map_add_early/hotplug

Hi Dave,

2012/07/12 22:40, Dave Hansen wrote:
> On 07/11/2012 09:52 PM, Yasuaki Ishimatsu wrote:
>> Does the following patch include your comment? If O.K., I will separate
>> the patch from the series and send it for bug fix.
> 
> Looks sane to me.  It does now mean that the calling conventions for
> some of the other firmware_map*() functions are different, but I think
> that's OK since they're only used internally to memmap.c.

Thank you for reviewing my patch.
I'll send the patch.

Thanks,
Yasuaki Ishimatsu

> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo <at> vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo <at> kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont <at> kvack.org"> email <at> kvack.org </a>

(Continue reading)

headers

Yasuaki Ishimatsu | 13 Jul 2012 06:34

Re: [RFC PATCH v3 3/13] memory-hotplug : unify argument of firmware_map_add_early/hotplug

Hi Dave,

2012/07/12 22:40, Dave Hansen wrote:
> On 07/11/2012 09:52 PM, Yasuaki Ishimatsu wrote:
>> Does the following patch include your comment? If O.K., I will separate
>> the patch from the series and send it for bug fix.
> 
> Looks sane to me.  It does now mean that the calling conventions for
> some of the other firmware_map*() functions are different, but I think
> that's OK since they're only used internally to memmap.c.

Thank you for reviewing my patch.
I'll send the patch.

Thanks,
Yasuaki Ishimatsu

> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo <at> vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

headers

Yasuaki Ishimatsu | 13 Jul 2012 07:11

Re: [RFC PATCH v3 3/13] memory-hotplug : unify argument of firmware_map_add_early/hotplug

Hi Dave,

2012/07/12 22:40, Dave Hansen wrote:
> On 07/11/2012 09:52 PM, Yasuaki Ishimatsu wrote:
>> Does the following patch include your comment? If O.K., I will separate
>> the patch from the series and send it for bug fix.
> 
> Looks sane to me.  It does now mean that the calling conventions for
> some of the other firmware_map*() functions are different, but I think
> that's OK since they're only used internally to memmap.c.

Can I add "Reviewed-by: Dave Hansen" to the patch?

Thanks,
Yasuaki Ishimatsu

> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo <at> vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo <at> kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont <at> kvack.org"> email <at> kvack.org </a>

(Continue reading)

headers

Yasuaki Ishimatsu | 13 Jul 2012 07:11

Re: [RFC PATCH v3 3/13] memory-hotplug : unify argument of firmware_map_add_early/hotplug

Hi Dave,

2012/07/12 22:40, Dave Hansen wrote:
> On 07/11/2012 09:52 PM, Yasuaki Ishimatsu wrote:
>> Does the following patch include your comment? If O.K., I will separate
>> the patch from the series and send it for bug fix.
> 
> Looks sane to me.  It does now mean that the calling conventions for
> some of the other firmware_map*() functions are different, but I think
> that's OK since they're only used internally to memmap.c.

Can I add "Reviewed-by: Dave Hansen" to the patch?

Thanks,
Yasuaki Ishimatsu

> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo <at> vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

headers

Dave Hansen | 12 Jul 2012 15:40

Re: [RFC PATCH v3 3/13] memory-hotplug : unify argument of firmware_map_add_early/hotplug

On 07/11/2012 09:52 PM, Yasuaki Ishimatsu wrote:
> Does the following patch include your comment? If O.K., I will separate
> the patch from the series and send it for bug fix.

Looks sane to me.  It does now mean that the calling conventions for
some of the other firmware_map*() functions are different, but I think
that's OK since they're only used internally to memmap.c.

headers

Yasuaki Ishimatsu | 12 Jul 2012 06:52

Re: [RFC PATCH v3 3/13] memory-hotplug : unify argument of firmware_map_add_early/hotplug

Hi Dave,

2012/07/12 0:30, Dave Hansen wrote:
> On 07/09/2012 03:25 AM, Yasuaki Ishimatsu wrote:
>>  <at>  <at>  -642,7 +642,7  <at>  <at>  int __ref add_memory(int nid, u64 start,
>>   	}
>>
>>   	/* create new memmap entry */
>> -	firmware_map_add_hotplug(start, start + size, "System RAM");
>> +	firmware_map_add_hotplug(start, start + size - 1, "System RAM");
> 
> I know the firmware_map_*() calls use inclusive end addresses
> internally, but do we really need to expose them?  Both of the callers
> you mentioned do:
> 
> 	firmware_map_add_hotplug(start, start + size - 1, "System RAM");
> 
> or
> 
>                  firmware_map_add_early(entry->addr,
>                          entry->addr + entry->size - 1,
>                          e820_type_to_string(entry->type));
> 
> So it seems a _bit_ silly to keep all of the callers doing this size-1
> thing.  I also noted that the new caller that you added does the same
> thing.  Could we just change the external calling convention to be
> exclusive?

Thank you for your comment.

(Continue reading)

headers

Dave Hansen | 11 Jul 2012 17:30

Re: [RFC PATCH v3 3/13] memory-hotplug : unify argument of firmware_map_add_early/hotplug

On 07/09/2012 03:25 AM, Yasuaki Ishimatsu wrote:
>  <at>  <at>  -642,7 +642,7  <at>  <at>  int __ref add_memory(int nid, u64 start,
>  	}
> 
>  	/* create new memmap entry */
> -	firmware_map_add_hotplug(start, start + size, "System RAM");
> +	firmware_map_add_hotplug(start, start + size - 1, "System RAM");

I know the firmware_map_*() calls use inclusive end addresses
internally, but do we really need to expose them?  Both of the callers
you mentioned do:

	firmware_map_add_hotplug(start, start + size - 1, "System RAM");

or

                firmware_map_add_early(entry->addr,
                        entry->addr + entry->size - 1,
                        e820_type_to_string(entry->type));

So it seems a _bit_ silly to keep all of the callers doing this size-1
thing.  I also noted that the new caller that you added does the same
thing.  Could we just change the external calling convention to be
exclusive?

BTW, this patch should probably be first in your series.  It's a real
bugfix.

headers

Yasuaki Ishimatsu | 9 Jul 2012 12:25

[RFC PATCH v3 3/13] memory-hotplug : unify argument of firmware_map_add_early/hotplug

There are two ways to create /sys/firmware/memmap/X sysfs:

  - firmware_map_add_early
    When the system starts, it is calledd from e820_reserve_resources()
  - firmware_map_add_hotplug
    When the memory is hot plugged, it is called from add_memory()

But these functions are called without unifying value of end argument as below:

  - end argument of firmware_map_add_early()   : start + size - 1
  - end argument of firmware_map_add_hogplug() : start + size

The patch unifies them to "start + size - 1".

CC: David Rientjes <rientjes <at> google.com>
CC: Jiang Liu <liuj97 <at> gmail.com>
CC: Len Brown <len.brown <at> intel.com>
CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
CC: Paul Mackerras <paulus <at> samba.org>
CC: Christoph Lameter <cl <at> linux.com>
Cc: Minchan Kim <minchan.kim <at> gmail.com>
CC: Andrew Morton <akpm <at> linux-foundation.org>
CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
CC: Wen Congyang <wency <at> cn.fujitsu.com>
Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>

---
 mm/memory_hotplug.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(Continue reading)

headers

Yasuaki Ishimatsu | 9 Jul 2012 12:26

[RFC PATCH v3 4/13] memory-hotplug : remove /sys/firmware/memmap/X sysfs

When (hot)adding memory into system, /sys/firmware/memmap/X/{end, start, type}
sysfs files are created. But there is no code to remove these files. The patch
implements the function to remove them.

Note : The code does not free firmware_map_entry since there is no way to free
       memory which is allocated by bootmem.

CC: David Rientjes <rientjes <at> google.com>
CC: Jiang Liu <liuj97 <at> gmail.com>
CC: Len Brown <len.brown <at> intel.com>
CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
CC: Paul Mackerras <paulus <at> samba.org>
CC: Christoph Lameter <cl <at> linux.com>
Cc: Minchan Kim <minchan.kim <at> gmail.com>
CC: Andrew Morton <akpm <at> linux-foundation.org>
CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
CC: Wen Congyang <wency <at> cn.fujitsu.com>
Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>

---
 drivers/firmware/memmap.c    |   78 ++++++++++++++++++++++++++++++++++++++++++-
 include/linux/firmware-map.h |    6 +++
 mm/memory_hotplug.c          |    6 ++-
 3 files changed, 88 insertions(+), 2 deletions(-)

Index: linux-3.5-rc6/mm/memory_hotplug.c
===================================================================
--- linux-3.5-rc6.orig/mm/memory_hotplug.c	2012-07-09 18:23:13.323844923 +0900
+++ linux-3.5-rc6/mm/memory_hotplug.c	2012-07-09 18:23:19.522767424 +0900
 <at>  <at>  -661,7 +661,11  <at>  <at>  EXPORT_SYMBOL_GPL(add_memory);

(Continue reading)

headers

Wen Congyang | 13 Jul 2012 11:10

Re: [RFC PATCH v3 4/13] memory-hotplug : remove /sys/firmware/memmap/X sysfs

At 07/09/2012 06:26 PM, Yasuaki Ishimatsu Wrote:
> When (hot)adding memory into system, /sys/firmware/memmap/X/{end, start, type}
> sysfs files are created. But there is no code to remove these files. The patch
> implements the function to remove them.
> 
> Note : The code does not free firmware_map_entry since there is no way to free
>        memory which is allocated by bootmem.
> 
> CC: David Rientjes <rientjes <at> google.com>
> CC: Jiang Liu <liuj97 <at> gmail.com>
> CC: Len Brown <len.brown <at> intel.com>
> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
> CC: Paul Mackerras <paulus <at> samba.org>
> CC: Christoph Lameter <cl <at> linux.com>
> Cc: Minchan Kim <minchan.kim <at> gmail.com>
> CC: Andrew Morton <akpm <at> linux-foundation.org>
> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
> CC: Wen Congyang <wency <at> cn.fujitsu.com>
> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>
> 
> ---
>  drivers/firmware/memmap.c    |   78 ++++++++++++++++++++++++++++++++++++++++++-
>  include/linux/firmware-map.h |    6 +++
>  mm/memory_hotplug.c          |    6 ++-
>  3 files changed, 88 insertions(+), 2 deletions(-)
> 
> Index: linux-3.5-rc6/mm/memory_hotplug.c
> ===================================================================
> --- linux-3.5-rc6.orig/mm/memory_hotplug.c	2012-07-09 18:23:13.323844923 +0900
> +++ linux-3.5-rc6/mm/memory_hotplug.c	2012-07-09 18:23:19.522767424 +0900

(Continue reading)

headers

Yasuaki Ishimatsu | 17 Jul 2012 02:28

Re: [RFC PATCH v3 4/13] memory-hotplug : remove /sys/firmware/memmap/X sysfs

Hi Wen,

2012/07/13 18:10, Wen Congyang wrote:
> At 07/09/2012 06:26 PM, Yasuaki Ishimatsu Wrote:
>> When (hot)adding memory into system, /sys/firmware/memmap/X/{end, start, type}
>> sysfs files are created. But there is no code to remove these files. The patch
>> implements the function to remove them.
>>
>> Note : The code does not free firmware_map_entry since there is no way to free
>>         memory which is allocated by bootmem.
>>
>> CC: David Rientjes <rientjes <at> google.com>
>> CC: Jiang Liu <liuj97 <at> gmail.com>
>> CC: Len Brown <len.brown <at> intel.com>
>> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
>> CC: Paul Mackerras <paulus <at> samba.org>
>> CC: Christoph Lameter <cl <at> linux.com>
>> Cc: Minchan Kim <minchan.kim <at> gmail.com>
>> CC: Andrew Morton <akpm <at> linux-foundation.org>
>> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
>> CC: Wen Congyang <wency <at> cn.fujitsu.com>
>> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>
>>
>> ---
>>   drivers/firmware/memmap.c    |   78 ++++++++++++++++++++++++++++++++++++++++++-
>>   include/linux/firmware-map.h |    6 +++
>>   mm/memory_hotplug.c          |    6 ++-
>>   3 files changed, 88 insertions(+), 2 deletions(-)
>>
>> Index: linux-3.5-rc6/mm/memory_hotplug.c

(Continue reading)

headers

Yasuaki Ishimatsu | 17 Jul 2012 02:28

Re: [RFC PATCH v3 4/13] memory-hotplug : remove /sys/firmware/memmap/X sysfs

Hi Wen,

2012/07/13 18:10, Wen Congyang wrote:
> At 07/09/2012 06:26 PM, Yasuaki Ishimatsu Wrote:
>> When (hot)adding memory into system, /sys/firmware/memmap/X/{end, start, type}
>> sysfs files are created. But there is no code to remove these files. The patch
>> implements the function to remove them.
>>
>> Note : The code does not free firmware_map_entry since there is no way to free
>>         memory which is allocated by bootmem.
>>
>> CC: David Rientjes <rientjes <at> google.com>
>> CC: Jiang Liu <liuj97 <at> gmail.com>
>> CC: Len Brown <len.brown <at> intel.com>
>> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
>> CC: Paul Mackerras <paulus <at> samba.org>
>> CC: Christoph Lameter <cl <at> linux.com>
>> Cc: Minchan Kim <minchan.kim <at> gmail.com>
>> CC: Andrew Morton <akpm <at> linux-foundation.org>
>> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
>> CC: Wen Congyang <wency <at> cn.fujitsu.com>
>> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>
>>
>> ---
>>   drivers/firmware/memmap.c    |   78 ++++++++++++++++++++++++++++++++++++++++++-
>>   include/linux/firmware-map.h |    6 +++
>>   mm/memory_hotplug.c          |    6 ++-
>>   3 files changed, 88 insertions(+), 2 deletions(-)
>>
>> Index: linux-3.5-rc6/mm/memory_hotplug.c

(Continue reading)

headers

Wen Congyang | 16 Jul 2012 04:32

Re: [RFC PATCH v3 4/13] memory-hotplug : remove /sys/firmware/memmap/X sysfs

At 07/09/2012 06:26 PM, Yasuaki Ishimatsu Wrote:
> When (hot)adding memory into system, /sys/firmware/memmap/X/{end, start, type}
> sysfs files are created. But there is no code to remove these files. The patch
> implements the function to remove them.
> 
> Note : The code does not free firmware_map_entry since there is no way to free
>        memory which is allocated by bootmem.
> 
> CC: David Rientjes <rientjes <at> google.com>
> CC: Jiang Liu <liuj97 <at> gmail.com>
> CC: Len Brown <len.brown <at> intel.com>
> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
> CC: Paul Mackerras <paulus <at> samba.org>
> CC: Christoph Lameter <cl <at> linux.com>
> Cc: Minchan Kim <minchan.kim <at> gmail.com>
> CC: Andrew Morton <akpm <at> linux-foundation.org>
> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
> CC: Wen Congyang <wency <at> cn.fujitsu.com>
> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>
> 
> ---
>  drivers/firmware/memmap.c    |   78 ++++++++++++++++++++++++++++++++++++++++++-
>  include/linux/firmware-map.h |    6 +++
>  mm/memory_hotplug.c          |    6 ++-
>  3 files changed, 88 insertions(+), 2 deletions(-)
> 
> Index: linux-3.5-rc6/mm/memory_hotplug.c
> ===================================================================
> --- linux-3.5-rc6.orig/mm/memory_hotplug.c	2012-07-09 18:23:13.323844923 +0900
> +++ linux-3.5-rc6/mm/memory_hotplug.c	2012-07-09 18:23:19.522767424 +0900

(Continue reading)

headers

Yasuaki Ishimatsu | 17 Jul 2012 02:30

Re: [RFC PATCH v3 4/13] memory-hotplug : remove /sys/firmware/memmap/X sysfs

Hi Wen,

2012/07/16 11:32, Wen Congyang wrote:
> At 07/09/2012 06:26 PM, Yasuaki Ishimatsu Wrote:
>> When (hot)adding memory into system, /sys/firmware/memmap/X/{end, start, type}
>> sysfs files are created. But there is no code to remove these files. The patch
>> implements the function to remove them.
>>
>> Note : The code does not free firmware_map_entry since there is no way to free
>>         memory which is allocated by bootmem.
>>
>> CC: David Rientjes <rientjes <at> google.com>
>> CC: Jiang Liu <liuj97 <at> gmail.com>
>> CC: Len Brown <len.brown <at> intel.com>
>> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
>> CC: Paul Mackerras <paulus <at> samba.org>
>> CC: Christoph Lameter <cl <at> linux.com>
>> Cc: Minchan Kim <minchan.kim <at> gmail.com>
>> CC: Andrew Morton <akpm <at> linux-foundation.org>
>> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
>> CC: Wen Congyang <wency <at> cn.fujitsu.com>
>> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>
>>
>> ---
>>   drivers/firmware/memmap.c    |   78 ++++++++++++++++++++++++++++++++++++++++++-
>>   include/linux/firmware-map.h |    6 +++
>>   mm/memory_hotplug.c          |    6 ++-
>>   3 files changed, 88 insertions(+), 2 deletions(-)
>>
>> Index: linux-3.5-rc6/mm/memory_hotplug.c

(Continue reading)

headers

Yasuaki Ishimatsu | 17 Jul 2012 02:30

Re: [RFC PATCH v3 4/13] memory-hotplug : remove /sys/firmware/memmap/X sysfs

Hi Wen,

2012/07/16 11:32, Wen Congyang wrote:
> At 07/09/2012 06:26 PM, Yasuaki Ishimatsu Wrote:
>> When (hot)adding memory into system, /sys/firmware/memmap/X/{end, start, type}
>> sysfs files are created. But there is no code to remove these files. The patch
>> implements the function to remove them.
>>
>> Note : The code does not free firmware_map_entry since there is no way to free
>>         memory which is allocated by bootmem.
>>
>> CC: David Rientjes <rientjes <at> google.com>
>> CC: Jiang Liu <liuj97 <at> gmail.com>
>> CC: Len Brown <len.brown <at> intel.com>
>> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
>> CC: Paul Mackerras <paulus <at> samba.org>
>> CC: Christoph Lameter <cl <at> linux.com>
>> Cc: Minchan Kim <minchan.kim <at> gmail.com>
>> CC: Andrew Morton <akpm <at> linux-foundation.org>
>> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
>> CC: Wen Congyang <wency <at> cn.fujitsu.com>
>> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>
>>
>> ---
>>   drivers/firmware/memmap.c    |   78 ++++++++++++++++++++++++++++++++++++++++++-
>>   include/linux/firmware-map.h |    6 +++
>>   mm/memory_hotplug.c          |    6 ++-
>>   3 files changed, 88 insertions(+), 2 deletions(-)
>>
>> Index: linux-3.5-rc6/mm/memory_hotplug.c

(Continue reading)

headers

Wen Congyang | 16 Jul 2012 04:32

Re: [RFC PATCH v3 4/13] memory-hotplug : remove /sys/firmware/memmap/X sysfs

At 07/09/2012 06:26 PM, Yasuaki Ishimatsu Wrote:
> When (hot)adding memory into system, /sys/firmware/memmap/X/{end, start, type}
> sysfs files are created. But there is no code to remove these files. The patch
> implements the function to remove them.
> 
> Note : The code does not free firmware_map_entry since there is no way to free
>        memory which is allocated by bootmem.
> 
> CC: David Rientjes <rientjes <at> google.com>
> CC: Jiang Liu <liuj97 <at> gmail.com>
> CC: Len Brown <len.brown <at> intel.com>
> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
> CC: Paul Mackerras <paulus <at> samba.org>
> CC: Christoph Lameter <cl <at> linux.com>
> Cc: Minchan Kim <minchan.kim <at> gmail.com>
> CC: Andrew Morton <akpm <at> linux-foundation.org>
> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
> CC: Wen Congyang <wency <at> cn.fujitsu.com>
> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>
> 
> ---
>  drivers/firmware/memmap.c    |   78 ++++++++++++++++++++++++++++++++++++++++++-
>  include/linux/firmware-map.h |    6 +++
>  mm/memory_hotplug.c          |    6 ++-
>  3 files changed, 88 insertions(+), 2 deletions(-)
> 
> Index: linux-3.5-rc6/mm/memory_hotplug.c
> ===================================================================
> --- linux-3.5-rc6.orig/mm/memory_hotplug.c	2012-07-09 18:23:13.323844923 +0900
> +++ linux-3.5-rc6/mm/memory_hotplug.c	2012-07-09 18:23:19.522767424 +0900

(Continue reading)

headers

Yasuaki Ishimatsu | 9 Jul 2012 12:26

[RFC PATCH v3 4/13] memory-hotplug : remove /sys/firmware/memmap/X sysfs

When (hot)adding memory into system, /sys/firmware/memmap/X/{end, start, type}
sysfs files are created. But there is no code to remove these files. The patch
implements the function to remove them.

Note : The code does not free firmware_map_entry since there is no way to free
       memory which is allocated by bootmem.

CC: David Rientjes <rientjes <at> google.com>
CC: Jiang Liu <liuj97 <at> gmail.com>
CC: Len Brown <len.brown <at> intel.com>
CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
CC: Paul Mackerras <paulus <at> samba.org>
CC: Christoph Lameter <cl <at> linux.com>
Cc: Minchan Kim <minchan.kim <at> gmail.com>
CC: Andrew Morton <akpm <at> linux-foundation.org>
CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
CC: Wen Congyang <wency <at> cn.fujitsu.com>
Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>

---
 drivers/firmware/memmap.c    |   78 ++++++++++++++++++++++++++++++++++++++++++-
 include/linux/firmware-map.h |    6 +++
 mm/memory_hotplug.c          |    6 ++-
 3 files changed, 88 insertions(+), 2 deletions(-)

Index: linux-3.5-rc6/mm/memory_hotplug.c
===================================================================
--- linux-3.5-rc6.orig/mm/memory_hotplug.c	2012-07-09 18:23:13.323844923 +0900
+++ linux-3.5-rc6/mm/memory_hotplug.c	2012-07-09 18:23:19.522767424 +0900
 <at>  <at>  -661,7 +661,11  <at>  <at>  EXPORT_SYMBOL_GPL(add_memory);

(Continue reading)

headers

Yasuaki Ishimatsu | 9 Jul 2012 12:26

[RFC PATCH v3 5/13] memory-hotplug : does not release memory region in PAGES_PER_SECTION chunks

Since applying a patch(de7f0cba96786c), release_mem_region() has been changed
as called in PAGES_PER_SECTION chunks because register_memory_resource() is
called in PAGES_PER_SECTION chunks by add_memory(). But it seems firmware
dependency. If CRS are written in the PAGES_PER_SECTION chunks in ACPI DSDT
Table, register_memory_resource() is called in PAGES_PER_SECTION chunks.
But if CRS are written in the DIMM unit in ACPI DSDT Table,
register_memory_resource() is called in DIMM unit. So release_mem_region()
should not be called in PAGES_PER_SECTION chunks. The patch fixes it.

CC: David Rientjes <rientjes <at> google.com>
CC: Jiang Liu <liuj97 <at> gmail.com>
CC: Len Brown <len.brown <at> intel.com>
CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
CC: Paul Mackerras <paulus <at> samba.org>
CC: Christoph Lameter <cl <at> linux.com>
Cc: Minchan Kim <minchan.kim <at> gmail.com>
CC: Andrew Morton <akpm <at> linux-foundation.org>
CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
CC: Wen Congyang <wency <at> cn.fujitsu.com>
Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>

---
 arch/powerpc/platforms/pseries/hotplug-memory.c |   13 +++++++++----
 mm/memory_hotplug.c                             |    4 ++--
 2 files changed, 11 insertions(+), 6 deletions(-)

Index: linux-3.5-rc4/mm/memory_hotplug.c
===================================================================
--- linux-3.5-rc4.orig/mm/memory_hotplug.c	2012-07-03 14:22:03.549198802 +0900
+++ linux-3.5-rc4/mm/memory_hotplug.c	2012-07-03 14:22:05.919169458 +0900

(Continue reading)

headers

Wen Congyang | 13 Jul 2012 05:42

Re: [RFC PATCH v3 5/13] memory-hotplug : does not release memory region in PAGES_PER_SECTION chunks

At 07/09/2012 06:26 PM, Yasuaki Ishimatsu Wrote:
> Since applying a patch(de7f0cba96786c), release_mem_region() has been changed
> as called in PAGES_PER_SECTION chunks because register_memory_resource() is
> called in PAGES_PER_SECTION chunks by add_memory(). But it seems firmware
> dependency. If CRS are written in the PAGES_PER_SECTION chunks in ACPI DSDT
> Table, register_memory_resource() is called in PAGES_PER_SECTION chunks.
> But if CRS are written in the DIMM unit in ACPI DSDT Table,
> register_memory_resource() is called in DIMM unit. So release_mem_region()
> should not be called in PAGES_PER_SECTION chunks. The patch fixes it.
> 
> CC: David Rientjes <rientjes <at> google.com>
> CC: Jiang Liu <liuj97 <at> gmail.com>
> CC: Len Brown <len.brown <at> intel.com>
> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
> CC: Paul Mackerras <paulus <at> samba.org>
> CC: Christoph Lameter <cl <at> linux.com>
> Cc: Minchan Kim <minchan.kim <at> gmail.com>
> CC: Andrew Morton <akpm <at> linux-foundation.org>
> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
> CC: Wen Congyang <wency <at> cn.fujitsu.com>
> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>
> 
> ---
>  arch/powerpc/platforms/pseries/hotplug-memory.c |   13 +++++++++----
>  mm/memory_hotplug.c                             |    4 ++--
>  2 files changed, 11 insertions(+), 6 deletions(-)
> 
> Index: linux-3.5-rc4/mm/memory_hotplug.c
> ===================================================================
> --- linux-3.5-rc4.orig/mm/memory_hotplug.c	2012-07-03 14:22:03.549198802 +0900

(Continue reading)

headers

Wen Congyang | 13 Jul 2012 05:42

Re: [RFC PATCH v3 5/13] memory-hotplug : does not release memory region in PAGES_PER_SECTION chunks

At 07/09/2012 06:26 PM, Yasuaki Ishimatsu Wrote:
> Since applying a patch(de7f0cba96786c), release_mem_region() has been changed
> as called in PAGES_PER_SECTION chunks because register_memory_resource() is
> called in PAGES_PER_SECTION chunks by add_memory(). But it seems firmware
> dependency. If CRS are written in the PAGES_PER_SECTION chunks in ACPI DSDT
> Table, register_memory_resource() is called in PAGES_PER_SECTION chunks.
> But if CRS are written in the DIMM unit in ACPI DSDT Table,
> register_memory_resource() is called in DIMM unit. So release_mem_region()
> should not be called in PAGES_PER_SECTION chunks. The patch fixes it.
> 
> CC: David Rientjes <rientjes <at> google.com>
> CC: Jiang Liu <liuj97 <at> gmail.com>
> CC: Len Brown <len.brown <at> intel.com>
> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
> CC: Paul Mackerras <paulus <at> samba.org>
> CC: Christoph Lameter <cl <at> linux.com>
> Cc: Minchan Kim <minchan.kim <at> gmail.com>
> CC: Andrew Morton <akpm <at> linux-foundation.org>
> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
> CC: Wen Congyang <wency <at> cn.fujitsu.com>
> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>
> 
> ---
>  arch/powerpc/platforms/pseries/hotplug-memory.c |   13 +++++++++----
>  mm/memory_hotplug.c                             |    4 ++--
>  2 files changed, 11 insertions(+), 6 deletions(-)
> 
> Index: linux-3.5-rc4/mm/memory_hotplug.c
> ===================================================================
> --- linux-3.5-rc4.orig/mm/memory_hotplug.c	2012-07-03 14:22:03.549198802 +0900

(Continue reading)

headers

Yasuaki Ishimatsu | 9 Jul 2012 12:26

[RFC PATCH v3 5/13] memory-hotplug : does not release memory region in PAGES_PER_SECTION chunks

Since applying a patch(de7f0cba96786c), release_mem_region() has been changed
as called in PAGES_PER_SECTION chunks because register_memory_resource() is
called in PAGES_PER_SECTION chunks by add_memory(). But it seems firmware
dependency. If CRS are written in the PAGES_PER_SECTION chunks in ACPI DSDT
Table, register_memory_resource() is called in PAGES_PER_SECTION chunks.
But if CRS are written in the DIMM unit in ACPI DSDT Table,
register_memory_resource() is called in DIMM unit. So release_mem_region()
should not be called in PAGES_PER_SECTION chunks. The patch fixes it.

CC: David Rientjes <rientjes <at> google.com>
CC: Jiang Liu <liuj97 <at> gmail.com>
CC: Len Brown <len.brown <at> intel.com>
CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
CC: Paul Mackerras <paulus <at> samba.org>
CC: Christoph Lameter <cl <at> linux.com>
Cc: Minchan Kim <minchan.kim <at> gmail.com>
CC: Andrew Morton <akpm <at> linux-foundation.org>
CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
CC: Wen Congyang <wency <at> cn.fujitsu.com>
Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>

---
 arch/powerpc/platforms/pseries/hotplug-memory.c |   13 +++++++++----
 mm/memory_hotplug.c                             |    4 ++--
 2 files changed, 11 insertions(+), 6 deletions(-)

Index: linux-3.5-rc4/mm/memory_hotplug.c
===================================================================
--- linux-3.5-rc4.orig/mm/memory_hotplug.c	2012-07-03 14:22:03.549198802 +0900
+++ linux-3.5-rc4/mm/memory_hotplug.c	2012-07-03 14:22:05.919169458 +0900

(Continue reading)

headers

Yasuaki Ishimatsu | 9 Jul 2012 12:27

[RFC PATCH v3 6/13] memory-hotplug : add memory_block_release

When calling remove_memory_block(), the function shows following message at
device_release().

Device 'memory528' does not have a release() function, it is broken and must
be fixed.

remove_memory_block() calls kfree(mem). I think it shouled be called from
device_release(). So the patch implements memory_block_release()

CC: David Rientjes <rientjes <at> google.com>
CC: Jiang Liu <liuj97 <at> gmail.com>
CC: Len Brown <len.brown <at> intel.com>
CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
CC: Paul Mackerras <paulus <at> samba.org>
CC: Christoph Lameter <cl <at> linux.com>
Cc: Minchan Kim <minchan.kim <at> gmail.com>
CC: Andrew Morton <akpm <at> linux-foundation.org>
CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
CC: Wen Congyang <wency <at> cn.fujitsu.com>
Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>

---
 drivers/base/memory.c |   11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)

Index: linux-3.5-rc6/drivers/base/memory.c
===================================================================
--- linux-3.5-rc6.orig/drivers/base/memory.c	2012-07-09 18:10:54.880076739 +0900
+++ linux-3.5-rc6/drivers/base/memory.c	2012-07-09 18:19:20.471755922 +0900
 <at>  <at>  -109,6 +109,15  <at>  <at>  bool is_memblk_offline(unsigned long sta

(Continue reading)

headers

Yasuaki Ishimatsu | 9 Jul 2012 12:27

[RFC PATCH v3 6/13] memory-hotplug : add memory_block_release

When calling remove_memory_block(), the function shows following message at
device_release().

Device 'memory528' does not have a release() function, it is broken and must
be fixed.

remove_memory_block() calls kfree(mem). I think it shouled be called from
device_release(). So the patch implements memory_block_release()

CC: David Rientjes <rientjes <at> google.com>
CC: Jiang Liu <liuj97 <at> gmail.com>
CC: Len Brown <len.brown <at> intel.com>
CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
CC: Paul Mackerras <paulus <at> samba.org>
CC: Christoph Lameter <cl <at> linux.com>
Cc: Minchan Kim <minchan.kim <at> gmail.com>
CC: Andrew Morton <akpm <at> linux-foundation.org>
CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
CC: Wen Congyang <wency <at> cn.fujitsu.com>
Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>

---
 drivers/base/memory.c |   11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)

Index: linux-3.5-rc6/drivers/base/memory.c
===================================================================
--- linux-3.5-rc6.orig/drivers/base/memory.c	2012-07-09 18:10:54.880076739 +0900
+++ linux-3.5-rc6/drivers/base/memory.c	2012-07-09 18:19:20.471755922 +0900
 <at>  <at>  -109,6 +109,15  <at>  <at>  bool is_memblk_offline(unsigned long sta

(Continue reading)

headers

Yasuaki Ishimatsu | 9 Jul 2012 12:28

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

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 defined, there is no way to remove a memmap.
So __remove_section only calls unregister_memory_section().

CC: David Rientjes <rientjes <at> google.com>
CC: Jiang Liu <liuj97 <at> gmail.com>
CC: Len Brown <len.brown <at> intel.com>
CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
CC: Paul Mackerras <paulus <at> samba.org>
CC: Christoph Lameter <cl <at> linux.com>
Cc: Minchan Kim <minchan.kim <at> gmail.com>
CC: Andrew Morton <akpm <at> linux-foundation.org>
CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
CC: Wen Congyang <wency <at> cn.fujitsu.com>
Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>

---
 arch/powerpc/platforms/pseries/hotplug-memory.c |    5 +----
 include/linux/memory_hotplug.h                  |    3 +--
 mm/memory_hotplug.c                             |   20 +++++++++++++-------
 3 files changed, 15 insertions(+), 13 deletions(-)

Index: linux-3.5-rc4/mm/memory_hotplug.c
===================================================================
--- linux-3.5-rc4.orig/mm/memory_hotplug.c	2012-07-03 14:22:05.919169458 +0900
+++ linux-3.5-rc4/mm/memory_hotplug.c	2012-07-03 14:22:10.170116406 +0900

(Continue reading)

headers

Yasuaki Ishimatsu | 9 Jul 2012 12:28

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

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 defined, there is no way to remove a memmap.
So __remove_section only calls unregister_memory_section().

CC: David Rientjes <rientjes <at> google.com>
CC: Jiang Liu <liuj97 <at> gmail.com>
CC: Len Brown <len.brown <at> intel.com>
CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
CC: Paul Mackerras <paulus <at> samba.org>
CC: Christoph Lameter <cl <at> linux.com>
Cc: Minchan Kim <minchan.kim <at> gmail.com>
CC: Andrew Morton <akpm <at> linux-foundation.org>
CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
CC: Wen Congyang <wency <at> cn.fujitsu.com>
Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>

---
 arch/powerpc/platforms/pseries/hotplug-memory.c |    5 +----
 include/linux/memory_hotplug.h                  |    3 +--
 mm/memory_hotplug.c                             |   20 +++++++++++++-------
 3 files changed, 15 insertions(+), 13 deletions(-)

Index: linux-3.5-rc4/mm/memory_hotplug.c
===================================================================
--- linux-3.5-rc4.orig/mm/memory_hotplug.c	2012-07-03 14:22:05.919169458 +0900
+++ linux-3.5-rc4/mm/memory_hotplug.c	2012-07-03 14:22:10.170116406 +0900

(Continue reading)

headers

Yasuaki Ishimatsu | 9 Jul 2012 12:29

[RFC PATCH v3 8/13] memory-hotplug : check page type in get_page_bootmem

There is a possibility that get_page_bootmem() is called to the same page many
times. So when get_page_bootmem is called to the same page, the function only
increments page->_count.

CC: David Rientjes <rientjes <at> google.com>
CC: Jiang Liu <liuj97 <at> gmail.com>
CC: Len Brown <len.brown <at> intel.com>
CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
CC: Paul Mackerras <paulus <at> samba.org>
CC: Christoph Lameter <cl <at> linux.com>
Cc: Minchan Kim <minchan.kim <at> gmail.com>
CC: Andrew Morton <akpm <at> linux-foundation.org>
CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
CC: Wen Congyang <wency <at> cn.fujitsu.com>
Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>

---
 mm/memory_hotplug.c |   15 +++++++++++----
 1 file changed, 11 insertions(+), 4 deletions(-)

Index: linux-3.5-rc4/mm/memory_hotplug.c
===================================================================
--- linux-3.5-rc4.orig/mm/memory_hotplug.c	2012-07-03 14:22:10.170116406 +0900
+++ linux-3.5-rc4/mm/memory_hotplug.c	2012-07-03 14:22:12.299089413 +0900
 <at>  <at>  -95,10 +95,17  <at>  <at>  static void release_memory_resource(stru
 static void get_page_bootmem(unsigned long info,  struct page *page,
 			     unsigned long type)
 {
-	page->lru.next = (struct list_head *) type;
-	SetPagePrivate(page);

(Continue reading)

headers

Yasuaki Ishimatsu | 9 Jul 2012 12:29

[RFC PATCH v3 8/13] memory-hotplug : check page type in get_page_bootmem

There is a possibility that get_page_bootmem() is called to the same page many
times. So when get_page_bootmem is called to the same page, the function only
increments page->_count.

CC: David Rientjes <rientjes <at> google.com>
CC: Jiang Liu <liuj97 <at> gmail.com>
CC: Len Brown <len.brown <at> intel.com>
CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
CC: Paul Mackerras <paulus <at> samba.org>
CC: Christoph Lameter <cl <at> linux.com>
Cc: Minchan Kim <minchan.kim <at> gmail.com>
CC: Andrew Morton <akpm <at> linux-foundation.org>
CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
CC: Wen Congyang <wency <at> cn.fujitsu.com>
Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>

---
 mm/memory_hotplug.c |   15 +++++++++++----
 1 file changed, 11 insertions(+), 4 deletions(-)

Index: linux-3.5-rc4/mm/memory_hotplug.c
===================================================================
--- linux-3.5-rc4.orig/mm/memory_hotplug.c	2012-07-03 14:22:10.170116406 +0900
+++ linux-3.5-rc4/mm/memory_hotplug.c	2012-07-03 14:22:12.299089413 +0900
 <at>  <at>  -95,10 +95,17  <at>  <at>  static void release_memory_resource(stru
 static void get_page_bootmem(unsigned long info,  struct page *page,
 			     unsigned long type)
 {
-	page->lru.next = (struct list_head *) type;
-	SetPagePrivate(page);

(Continue reading)

headers

Yasuaki Ishimatsu | 9 Jul 2012 12:30

[RFC PATCH v3 9/13] memory-hotplug : move register_page_bootmem_info_node and put_page_bootmem for sparse-vmemmap

For implementing register_page_bootmem_info_node of sparse-vmemmap,
register_page_bootmem_info_node and put_page_bootmem are moved to
memory_hotplug.c

CC: David Rientjes <rientjes <at> google.com>
CC: Jiang Liu <liuj97 <at> gmail.com>
CC: Len Brown <len.brown <at> intel.com>
CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
CC: Paul Mackerras <paulus <at> samba.org>
CC: Christoph Lameter <cl <at> linux.com>
Cc: Minchan Kim <minchan.kim <at> gmail.com>
CC: Andrew Morton <akpm <at> linux-foundation.org>
CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
CC: Wen Congyang <wency <at> cn.fujitsu.com>
Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>

---
 include/linux/memory_hotplug.h |    9 ---------
 mm/memory_hotplug.c            |    8 ++++++--
 2 files changed, 6 insertions(+), 11 deletions(-)

Index: linux-3.5-rc4/include/linux/memory_hotplug.h
===================================================================
--- linux-3.5-rc4.orig/include/linux/memory_hotplug.h	2012-07-03 14:22:10.170116406 +0900
+++ linux-3.5-rc4/include/linux/memory_hotplug.h	2012-07-03 14:22:14.409063086 +0900
 <at>  <at>  -160,17 +160,8  <at>  <at>  static inline void arch_refresh_nodedata
 #endif /* CONFIG_NUMA */
 #endif /* CONFIG_HAVE_ARCH_NODEDATA_EXTENSION */

-#ifdef CONFIG_SPARSEMEM_VMEMMAP

(Continue reading)

headers

Yasuaki Ishimatsu | 9 Jul 2012 12:30

[RFC PATCH v3 9/13] memory-hotplug : move register_page_bootmem_info_node and put_page_bootmem for sparse-vmemmap

For implementing register_page_bootmem_info_node of sparse-vmemmap,
register_page_bootmem_info_node and put_page_bootmem are moved to
memory_hotplug.c

CC: David Rientjes <rientjes <at> google.com>
CC: Jiang Liu <liuj97 <at> gmail.com>
CC: Len Brown <len.brown <at> intel.com>
CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
CC: Paul Mackerras <paulus <at> samba.org>
CC: Christoph Lameter <cl <at> linux.com>
Cc: Minchan Kim <minchan.kim <at> gmail.com>
CC: Andrew Morton <akpm <at> linux-foundation.org>
CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
CC: Wen Congyang <wency <at> cn.fujitsu.com>
Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>

---
 include/linux/memory_hotplug.h |    9 ---------
 mm/memory_hotplug.c            |    8 ++++++--
 2 files changed, 6 insertions(+), 11 deletions(-)

Index: linux-3.5-rc4/include/linux/memory_hotplug.h
===================================================================
--- linux-3.5-rc4.orig/include/linux/memory_hotplug.h	2012-07-03 14:22:10.170116406 +0900
+++ linux-3.5-rc4/include/linux/memory_hotplug.h	2012-07-03 14:22:14.409063086 +0900
 <at>  <at>  -160,17 +160,8  <at>  <at>  static inline void arch_refresh_nodedata
 #endif /* CONFIG_NUMA */
 #endif /* CONFIG_HAVE_ARCH_NODEDATA_EXTENSION */

-#ifdef CONFIG_SPARSEMEM_VMEMMAP

(Continue reading)

headers

Yasuaki Ishimatsu | 9 Jul 2012 12:32

[RFC PATCH v3 10/13] memory-hotplug : implement register_page_bootmem_info_section of sparse-vmemmap

For removing memmap region of sparse-vmemmap which is allocated bootmem,
memmap region of sparse-vmemmap needs to be registered by get_page_bootmem().
So the patch searches pages of virtual mapping and registers the pages by
get_page_bootmem().

CC: David Rientjes <rientjes <at> google.com>
CC: Jiang Liu <liuj97 <at> gmail.com>
CC: Len Brown <len.brown <at> intel.com>
CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
CC: Paul Mackerras <paulus <at> samba.org>
CC: Christoph Lameter <cl <at> linux.com>
Cc: Minchan Kim <minchan.kim <at> gmail.com>
CC: Andrew Morton <akpm <at> linux-foundation.org>
CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
CC: Wen Congyang <wency <at> cn.fujitsu.com>
Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>

---
 arch/x86/mm/init_64.c          |   53 +++++++++++++++++++++++++++++++++++++++++
 include/linux/memory_hotplug.h |    2 +
 include/linux/mm.h             |    3 +-
 mm/memory_hotplug.c            |   23 +++++++++++++++--
 4 files changed, 77 insertions(+), 4 deletions(-)

Index: linux-3.5-rc4/mm/memory_hotplug.c
===================================================================
--- linux-3.5-rc4.orig/mm/memory_hotplug.c	2012-07-03 14:22:14.419062959 +0900
+++ linux-3.5-rc4/mm/memory_hotplug.c	2012-07-03 14:22:18.522011667 +0900
 <at>  <at>  -91,8 +91,8  <at>  <at>  static void release_memory_resource(stru
 }

(Continue reading)

headers

Yasuaki Ishimatsu | 9 Jul 2012 12:32

[RFC PATCH v3 10/13] memory-hotplug : implement register_page_bootmem_info_section of sparse-vmemmap

For removing memmap region of sparse-vmemmap which is allocated bootmem,
memmap region of sparse-vmemmap needs to be registered by get_page_bootmem().
So the patch searches pages of virtual mapping and registers the pages by
get_page_bootmem().

CC: David Rientjes <rientjes <at> google.com>
CC: Jiang Liu <liuj97 <at> gmail.com>
CC: Len Brown <len.brown <at> intel.com>
CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
CC: Paul Mackerras <paulus <at> samba.org>
CC: Christoph Lameter <cl <at> linux.com>
Cc: Minchan Kim <minchan.kim <at> gmail.com>
CC: Andrew Morton <akpm <at> linux-foundation.org>
CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
CC: Wen Congyang <wency <at> cn.fujitsu.com>
Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>

---
 arch/x86/mm/init_64.c          |   53 +++++++++++++++++++++++++++++++++++++++++
 include/linux/memory_hotplug.h |    2 +
 include/linux/mm.h             |    3 +-
 mm/memory_hotplug.c            |   23 +++++++++++++++--
 4 files changed, 77 insertions(+), 4 deletions(-)

Index: linux-3.5-rc4/mm/memory_hotplug.c
===================================================================
--- linux-3.5-rc4.orig/mm/memory_hotplug.c	2012-07-03 14:22:14.419062959 +0900
+++ linux-3.5-rc4/mm/memory_hotplug.c	2012-07-03 14:22:18.522011667 +0900
 <at>  <at>  -91,8 +91,8  <at>  <at>  static void release_memory_resource(stru
 }

(Continue reading)

headers

Yasuaki Ishimatsu | 9 Jul 2012 12:33

[RFC PATCH v3 11/13] memory-hotplug : free memmap of sparse-vmemmap

I don't think that all pages of virtual mapping in removed memory can be
freed, since page which type is MIX_SECTION_INFO is difficult to free.
So, the patch only frees page which type is SECTION_INFO at first.

CC: David Rientjes <rientjes <at> google.com>
CC: Jiang Liu <liuj97 <at> gmail.com>
CC: Len Brown <len.brown <at> intel.com>
CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
CC: Paul Mackerras <paulus <at> samba.org>
CC: Christoph Lameter <cl <at> linux.com>
Cc: Minchan Kim <minchan.kim <at> gmail.com>
CC: Andrew Morton <akpm <at> linux-foundation.org>
CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
CC: Wen Congyang <wency <at> cn.fujitsu.com>
Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>

---
 arch/x86/mm/init_64.c |   91 ++++++++++++++++++++++++++++++++++++++++++++++++++
 include/linux/mm.h    |    2 +
 mm/memory_hotplug.c   |    5 ++
 mm/sparse.c           |    5 +-
 4 files changed, 101 insertions(+), 2 deletions(-)

Index: linux-3.5-rc4/include/linux/mm.h
===================================================================
--- linux-3.5-rc4.orig/include/linux/mm.h	2012-07-03 14:22:18.530011567 +0900
+++ linux-3.5-rc4/include/linux/mm.h	2012-07-03 14:22:20.999983872 +0900
 <at>  <at>  -1588,6 +1588,8  <at>  <at>  int vmemmap_populate(struct page *start_
 void vmemmap_populate_print_last(void);
 void register_page_bootmem_memmap(unsigned long section_nr, struct page *map,

(Continue reading)

headers

Wen Congyang | 11 Jul 2012 07:06

Re: [RFC PATCH v3 11/13] memory-hotplug : free memmap of sparse-vmemmap

At 07/09/2012 06:33 PM, Yasuaki Ishimatsu Wrote:
> I don't think that all pages of virtual mapping in removed memory can be
> freed, since page which type is MIX_SECTION_INFO is difficult to free.
> So, the patch only frees page which type is SECTION_INFO at first.
> 
> CC: David Rientjes <rientjes <at> google.com>
> CC: Jiang Liu <liuj97 <at> gmail.com>
> CC: Len Brown <len.brown <at> intel.com>
> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
> CC: Paul Mackerras <paulus <at> samba.org>
> CC: Christoph Lameter <cl <at> linux.com>
> Cc: Minchan Kim <minchan.kim <at> gmail.com>
> CC: Andrew Morton <akpm <at> linux-foundation.org>
> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
> CC: Wen Congyang <wency <at> cn.fujitsu.com>
> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>
> 
> ---
>  arch/x86/mm/init_64.c |   91 ++++++++++++++++++++++++++++++++++++++++++++++++++
>  include/linux/mm.h    |    2 +
>  mm/memory_hotplug.c   |    5 ++
>  mm/sparse.c           |    5 +-
>  4 files changed, 101 insertions(+), 2 deletions(-)
> 
> Index: linux-3.5-rc4/include/linux/mm.h
> ===================================================================
> --- linux-3.5-rc4.orig/include/linux/mm.h	2012-07-03 14:22:18.530011567 +0900
> +++ linux-3.5-rc4/include/linux/mm.h	2012-07-03 14:22:20.999983872 +0900
>  <at>  <at>  -1588,6 +1588,8  <at>  <at>  int vmemmap_populate(struct page *start_
>  void vmemmap_populate_print_last(void);

(Continue reading)

headers

Yasuaki Ishimatsu | 11 Jul 2012 07:52

Re: [RFC PATCH v3 11/13] memory-hotplug : free memmap of sparse-vmemmap

2012/07/11 14:06, Wen Congyang wrote:
Hi Wen,

> At 07/09/2012 06:33 PM, Yasuaki Ishimatsu Wrote:
>> I don't think that all pages of virtual mapping in removed memory can be
>> freed, since page which type is MIX_SECTION_INFO is difficult to free.
>> So, the patch only frees page which type is SECTION_INFO at first.
>>
>> CC: David Rientjes <rientjes <at> google.com>
>> CC: Jiang Liu <liuj97 <at> gmail.com>
>> CC: Len Brown <len.brown <at> intel.com>
>> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
>> CC: Paul Mackerras <paulus <at> samba.org>
>> CC: Christoph Lameter <cl <at> linux.com>
>> Cc: Minchan Kim <minchan.kim <at> gmail.com>
>> CC: Andrew Morton <akpm <at> linux-foundation.org>
>> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
>> CC: Wen Congyang <wency <at> cn.fujitsu.com>
>> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>
>>
>> ---
>>   arch/x86/mm/init_64.c |   91 ++++++++++++++++++++++++++++++++++++++++++++++++++
>>   include/linux/mm.h    |    2 +
>>   mm/memory_hotplug.c   |    5 ++
>>   mm/sparse.c           |    5 +-
>>   4 files changed, 101 insertions(+), 2 deletions(-)
>>
>> Index: linux-3.5-rc4/include/linux/mm.h
>> ===================================================================
>> --- linux-3.5-rc4.orig/include/linux/mm.h	2012-07-03 14:22:18.530011567 +0900

(Continue reading)

headers

Wen Congyang | 11 Jul 2012 08:25

Re: [RFC PATCH v3 11/13] memory-hotplug : free memmap of sparse-vmemmap

At 07/11/2012 01:52 PM, Yasuaki Ishimatsu Wrote:
> 2012/07/11 14:06, Wen Congyang wrote:
> Hi Wen,
> 
>> At 07/09/2012 06:33 PM, Yasuaki Ishimatsu Wrote:
>>> I don't think that all pages of virtual mapping in removed memory can be
>>> freed, since page which type is MIX_SECTION_INFO is difficult to free.
>>> So, the patch only frees page which type is SECTION_INFO at first.
>>>
>>> CC: David Rientjes <rientjes <at> google.com>
>>> CC: Jiang Liu <liuj97 <at> gmail.com>
>>> CC: Len Brown <len.brown <at> intel.com>
>>> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
>>> CC: Paul Mackerras <paulus <at> samba.org>
>>> CC: Christoph Lameter <cl <at> linux.com>
>>> Cc: Minchan Kim <minchan.kim <at> gmail.com>
>>> CC: Andrew Morton <akpm <at> linux-foundation.org>
>>> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
>>> CC: Wen Congyang <wency <at> cn.fujitsu.com>
>>> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>
>>>
>>> ---
>>>   arch/x86/mm/init_64.c |   91 ++++++++++++++++++++++++++++++++++++++++++++++++++
>>>   include/linux/mm.h    |    2 +
>>>   mm/memory_hotplug.c   |    5 ++
>>>   mm/sparse.c           |    5 +-
>>>   4 files changed, 101 insertions(+), 2 deletions(-)
>>>
>>> Index: linux-3.5-rc4/include/linux/mm.h
>>> ===================================================================

(Continue reading)

headers

Yasuaki Ishimatsu | 11 Jul 2012 08:48

Re: [RFC PATCH v3 11/13] memory-hotplug : free memmap of sparse-vmemmap

Hi Wen,

2012/07/11 15:25, Wen Congyang wrote:
> At 07/11/2012 01:52 PM, Yasuaki Ishimatsu Wrote:
>> 2012/07/11 14:06, Wen Congyang wrote:
>> Hi Wen,
>>
>>> At 07/09/2012 06:33 PM, Yasuaki Ishimatsu Wrote:
>>>> I don't think that all pages of virtual mapping in removed memory can be
>>>> freed, since page which type is MIX_SECTION_INFO is difficult to free.
>>>> So, the patch only frees page which type is SECTION_INFO at first.
>>>>
>>>> CC: David Rientjes <rientjes <at> google.com>
>>>> CC: Jiang Liu <liuj97 <at> gmail.com>
>>>> CC: Len Brown <len.brown <at> intel.com>
>>>> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
>>>> CC: Paul Mackerras <paulus <at> samba.org>
>>>> CC: Christoph Lameter <cl <at> linux.com>
>>>> Cc: Minchan Kim <minchan.kim <at> gmail.com>
>>>> CC: Andrew Morton <akpm <at> linux-foundation.org>
>>>> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
>>>> CC: Wen Congyang <wency <at> cn.fujitsu.com>
>>>> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>
>>>>
>>>> ---
>>>>    arch/x86/mm/init_64.c |   91 ++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>    include/linux/mm.h    |    2 +
>>>>    mm/memory_hotplug.c   |    5 ++
>>>>    mm/sparse.c           |    5 +-
>>>>    4 files changed, 101 insertions(+), 2 deletions(-)

(Continue reading)

headers

Wen Congyang | 11 Jul 2012 09:27

Re: [RFC PATCH v3 11/13] memory-hotplug : free memmap of sparse-vmemmap

At 07/11/2012 02:48 PM, Yasuaki Ishimatsu Wrote:
> Hi Wen,
> 
> 2012/07/11 15:25, Wen Congyang wrote:
>> At 07/11/2012 01:52 PM, Yasuaki Ishimatsu Wrote:
>>> 2012/07/11 14:06, Wen Congyang wrote:
>>> Hi Wen,
>>>
>>>> At 07/09/2012 06:33 PM, Yasuaki Ishimatsu Wrote:
>>>>> I don't think that all pages of virtual mapping in removed memory can be
>>>>> freed, since page which type is MIX_SECTION_INFO is difficult to free.
>>>>> So, the patch only frees page which type is SECTION_INFO at first.
>>>>>
>>>>> CC: David Rientjes <rientjes <at> google.com>
>>>>> CC: Jiang Liu <liuj97 <at> gmail.com>
>>>>> CC: Len Brown <len.brown <at> intel.com>
>>>>> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
>>>>> CC: Paul Mackerras <paulus <at> samba.org>
>>>>> CC: Christoph Lameter <cl <at> linux.com>
>>>>> Cc: Minchan Kim <minchan.kim <at> gmail.com>
>>>>> CC: Andrew Morton <akpm <at> linux-foundation.org>
>>>>> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
>>>>> CC: Wen Congyang <wency <at> cn.fujitsu.com>
>>>>> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>
>>>>>
>>>>> ---
>>>>>    arch/x86/mm/init_64.c |   91 ++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>    include/linux/mm.h    |    2 +
>>>>>    mm/memory_hotplug.c   |    5 ++
>>>>>    mm/sparse.c           |    5 +-

(Continue reading)

headers

Wen Congyang | 11 Jul 2012 09:27

Re: [RFC PATCH v3 11/13] memory-hotplug : free memmap of sparse-vmemmap

At 07/11/2012 02:48 PM, Yasuaki Ishimatsu Wrote:
> Hi Wen,
> 
> 2012/07/11 15:25, Wen Congyang wrote:
>> At 07/11/2012 01:52 PM, Yasuaki Ishimatsu Wrote:
>>> 2012/07/11 14:06, Wen Congyang wrote:
>>> Hi Wen,
>>>
>>>> At 07/09/2012 06:33 PM, Yasuaki Ishimatsu Wrote:
>>>>> I don't think that all pages of virtual mapping in removed memory can be
>>>>> freed, since page which type is MIX_SECTION_INFO is difficult to free.
>>>>> So, the patch only frees page which type is SECTION_INFO at first.
>>>>>
>>>>> CC: David Rientjes <rientjes <at> google.com>
>>>>> CC: Jiang Liu <liuj97 <at> gmail.com>
>>>>> CC: Len Brown <len.brown <at> intel.com>
>>>>> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
>>>>> CC: Paul Mackerras <paulus <at> samba.org>
>>>>> CC: Christoph Lameter <cl <at> linux.com>
>>>>> Cc: Minchan Kim <minchan.kim <at> gmail.com>
>>>>> CC: Andrew Morton <akpm <at> linux-foundation.org>
>>>>> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
>>>>> CC: Wen Congyang <wency <at> cn.fujitsu.com>
>>>>> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>
>>>>>
>>>>> ---
>>>>>    arch/x86/mm/init_64.c |   91 ++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>    include/linux/mm.h    |    2 +
>>>>>    mm/memory_hotplug.c   |    5 ++
>>>>>    mm/sparse.c           |    5 +-

(Continue reading)

headers

Yasuaki Ishimatsu | 11 Jul 2012 08:48

Re: [RFC PATCH v3 11/13] memory-hotplug : free memmap of sparse-vmemmap

Hi Wen,

2012/07/11 15:25, Wen Congyang wrote:
> At 07/11/2012 01:52 PM, Yasuaki Ishimatsu Wrote:
>> 2012/07/11 14:06, Wen Congyang wrote:
>> Hi Wen,
>>
>>> At 07/09/2012 06:33 PM, Yasuaki Ishimatsu Wrote:
>>>> I don't think that all pages of virtual mapping in removed memory can be
>>>> freed, since page which type is MIX_SECTION_INFO is difficult to free.
>>>> So, the patch only frees page which type is SECTION_INFO at first.
>>>>
>>>> CC: David Rientjes <rientjes <at> google.com>
>>>> CC: Jiang Liu <liuj97 <at> gmail.com>
>>>> CC: Len Brown <len.brown <at> intel.com>
>>>> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
>>>> CC: Paul Mackerras <paulus <at> samba.org>
>>>> CC: Christoph Lameter <cl <at> linux.com>
>>>> Cc: Minchan Kim <minchan.kim <at> gmail.com>
>>>> CC: Andrew Morton <akpm <at> linux-foundation.org>
>>>> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
>>>> CC: Wen Congyang <wency <at> cn.fujitsu.com>
>>>> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>
>>>>
>>>> ---
>>>>    arch/x86/mm/init_64.c |   91 ++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>    include/linux/mm.h    |    2 +
>>>>    mm/memory_hotplug.c   |    5 ++
>>>>    mm/sparse.c           |    5 +-
>>>>    4 files changed, 101 insertions(+), 2 deletions(-)

(Continue reading)

headers

Wen Congyang | 11 Jul 2012 08:25

Re: [RFC PATCH v3 11/13] memory-hotplug : free memmap of sparse-vmemmap

At 07/11/2012 01:52 PM, Yasuaki Ishimatsu Wrote:
> 2012/07/11 14:06, Wen Congyang wrote:
> Hi Wen,
> 
>> At 07/09/2012 06:33 PM, Yasuaki Ishimatsu Wrote:
>>> I don't think that all pages of virtual mapping in removed memory can be
>>> freed, since page which type is MIX_SECTION_INFO is difficult to free.
>>> So, the patch only frees page which type is SECTION_INFO at first.
>>>
>>> CC: David Rientjes <rientjes <at> google.com>
>>> CC: Jiang Liu <liuj97 <at> gmail.com>
>>> CC: Len Brown <len.brown <at> intel.com>
>>> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
>>> CC: Paul Mackerras <paulus <at> samba.org>
>>> CC: Christoph Lameter <cl <at> linux.com>
>>> Cc: Minchan Kim <minchan.kim <at> gmail.com>
>>> CC: Andrew Morton <akpm <at> linux-foundation.org>
>>> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
>>> CC: Wen Congyang <wency <at> cn.fujitsu.com>
>>> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>
>>>
>>> ---
>>>   arch/x86/mm/init_64.c |   91 ++++++++++++++++++++++++++++++++++++++++++++++++++
>>>   include/linux/mm.h    |    2 +
>>>   mm/memory_hotplug.c   |    5 ++
>>>   mm/sparse.c           |    5 +-
>>>   4 files changed, 101 insertions(+), 2 deletions(-)
>>>
>>> Index: linux-3.5-rc4/include/linux/mm.h
>>> ===================================================================

(Continue reading)

headers

Yasuaki Ishimatsu | 11 Jul 2012 07:52

Re: [RFC PATCH v3 11/13] memory-hotplug : free memmap of sparse-vmemmap

2012/07/11 14:06, Wen Congyang wrote:
Hi Wen,

> At 07/09/2012 06:33 PM, Yasuaki Ishimatsu Wrote:
>> I don't think that all pages of virtual mapping in removed memory can be
>> freed, since page which type is MIX_SECTION_INFO is difficult to free.
>> So, the patch only frees page which type is SECTION_INFO at first.
>>
>> CC: David Rientjes <rientjes <at> google.com>
>> CC: Jiang Liu <liuj97 <at> gmail.com>
>> CC: Len Brown <len.brown <at> intel.com>
>> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
>> CC: Paul Mackerras <paulus <at> samba.org>
>> CC: Christoph Lameter <cl <at> linux.com>
>> Cc: Minchan Kim <minchan.kim <at> gmail.com>
>> CC: Andrew Morton <akpm <at> linux-foundation.org>
>> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
>> CC: Wen Congyang <wency <at> cn.fujitsu.com>
>> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>
>>
>> ---
>>   arch/x86/mm/init_64.c |   91 ++++++++++++++++++++++++++++++++++++++++++++++++++
>>   include/linux/mm.h    |    2 +
>>   mm/memory_hotplug.c   |    5 ++
>>   mm/sparse.c           |    5 +-
>>   4 files changed, 101 insertions(+), 2 deletions(-)
>>
>> Index: linux-3.5-rc4/include/linux/mm.h
>> ===================================================================
>> --- linux-3.5-rc4.orig/include/linux/mm.h	2012-07-03 14:22:18.530011567 +0900

(Continue reading)

headers

Wen Congyang | 11 Jul 2012 07:06

Re: [RFC PATCH v3 11/13] memory-hotplug : free memmap of sparse-vmemmap

At 07/09/2012 06:33 PM, Yasuaki Ishimatsu Wrote:
> I don't think that all pages of virtual mapping in removed memory can be
> freed, since page which type is MIX_SECTION_INFO is difficult to free.
> So, the patch only frees page which type is SECTION_INFO at first.
> 
> CC: David Rientjes <rientjes <at> google.com>
> CC: Jiang Liu <liuj97 <at> gmail.com>
> CC: Len Brown <len.brown <at> intel.com>
> CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
> CC: Paul Mackerras <paulus <at> samba.org>
> CC: Christoph Lameter <cl <at> linux.com>
> Cc: Minchan Kim <minchan.kim <at> gmail.com>
> CC: Andrew Morton <akpm <at> linux-foundation.org>
> CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
> CC: Wen Congyang <wency <at> cn.fujitsu.com>
> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>
> 
> ---
>  arch/x86/mm/init_64.c |   91 ++++++++++++++++++++++++++++++++++++++++++++++++++
>  include/linux/mm.h    |    2 +
>  mm/memory_hotplug.c   |    5 ++
>  mm/sparse.c           |    5 +-
>  4 files changed, 101 insertions(+), 2 deletions(-)
> 
> Index: linux-3.5-rc4/include/linux/mm.h
> ===================================================================
> --- linux-3.5-rc4.orig/include/linux/mm.h	2012-07-03 14:22:18.530011567 +0900
> +++ linux-3.5-rc4/include/linux/mm.h	2012-07-03 14:22:20.999983872 +0900
>  <at>  <at>  -1588,6 +1588,8  <at>  <at>  int vmemmap_populate(struct page *start_
>  void vmemmap_populate_print_last(void);

(Continue reading)

headers

Yasuaki Ishimatsu | 9 Jul 2012 12:33

[RFC PATCH v3 11/13] memory-hotplug : free memmap of sparse-vmemmap

I don't think that all pages of virtual mapping in removed memory can be
freed, since page which type is MIX_SECTION_INFO is difficult to free.
So, the patch only frees page which type is SECTION_INFO at first.

CC: David Rientjes <rientjes <at> google.com>
CC: Jiang Liu <liuj97 <at> gmail.com>
CC: Len Brown <len.brown <at> intel.com>
CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
CC: Paul Mackerras <paulus <at> samba.org>
CC: Christoph Lameter <cl <at> linux.com>
Cc: Minchan Kim <minchan.kim <at> gmail.com>
CC: Andrew Morton <akpm <at> linux-foundation.org>
CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
CC: Wen Congyang <wency <at> cn.fujitsu.com>
Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>

---
 arch/x86/mm/init_64.c |   91 ++++++++++++++++++++++++++++++++++++++++++++++++++
 include/linux/mm.h    |    2 +
 mm/memory_hotplug.c   |    5 ++
 mm/sparse.c           |    5 +-
 4 files changed, 101 insertions(+), 2 deletions(-)

Index: linux-3.5-rc4/include/linux/mm.h
===================================================================
--- linux-3.5-rc4.orig/include/linux/mm.h	2012-07-03 14:22:18.530011567 +0900
+++ linux-3.5-rc4/include/linux/mm.h	2012-07-03 14:22:20.999983872 +0900
 <at>  <at>  -1588,6 +1588,8  <at>  <at>  int vmemmap_populate(struct page *start_
 void vmemmap_populate_print_last(void);
 void register_page_bootmem_memmap(unsigned long section_nr, struct page *map,

(Continue reading)

headers

Yasuaki Ishimatsu | 9 Jul 2012 12:34

[RFC PATCH v3 12/13] memory-hotplug : add node_device_release

When calling unregister_node(), the function shows following message at
device_release().

Device 'node2' does not have a release() function, it is broken and must be
fixed.

So the patch implements node_device_release()

CC: David Rientjes <rientjes <at> google.com>
CC: Jiang Liu <liuj97 <at> gmail.com>
CC: Len Brown <len.brown <at> intel.com>
CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
CC: Paul Mackerras <paulus <at> samba.org>
CC: Christoph Lameter <cl <at> linux.com>
Cc: Minchan Kim <minchan.kim <at> gmail.com>
CC: Andrew Morton <akpm <at> linux-foundation.org>
CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
CC: Wen Congyang <wency <at> cn.fujitsu.com>
Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>

---
 drivers/base/node.c |    7 +++++++
 1 file changed, 7 insertions(+)

Index: linux-3.5-rc4/drivers/base/node.c
===================================================================
--- linux-3.5-rc4.orig/drivers/base/node.c	2012-07-03 14:21:44.882432167 +0900
+++ linux-3.5-rc4/drivers/base/node.c	2012-07-03 14:22:23.296951921 +0900
 <at>  <at>  -252,6 +252,12  <at>  <at>  static inline void hugetlb_register_node
 static inline void hugetlb_unregister_node(struct node *node) {}

(Continue reading)

headers

Yasuaki Ishimatsu | 9 Jul 2012 12:34

[RFC PATCH v3 12/13] memory-hotplug : add node_device_release

When calling unregister_node(), the function shows following message at
device_release().

Device 'node2' does not have a release() function, it is broken and must be
fixed.

So the patch implements node_device_release()

CC: David Rientjes <rientjes <at> google.com>
CC: Jiang Liu <liuj97 <at> gmail.com>
CC: Len Brown <len.brown <at> intel.com>
CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
CC: Paul Mackerras <paulus <at> samba.org>
CC: Christoph Lameter <cl <at> linux.com>
Cc: Minchan Kim <minchan.kim <at> gmail.com>
CC: Andrew Morton <akpm <at> linux-foundation.org>
CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
CC: Wen Congyang <wency <at> cn.fujitsu.com>
Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>

---
 drivers/base/node.c |    7 +++++++
 1 file changed, 7 insertions(+)

Index: linux-3.5-rc4/drivers/base/node.c
===================================================================
--- linux-3.5-rc4.orig/drivers/base/node.c	2012-07-03 14:21:44.882432167 +0900
+++ linux-3.5-rc4/drivers/base/node.c	2012-07-03 14:22:23.296951921 +0900
 <at>  <at>  -252,6 +252,12  <at>  <at>  static inline void hugetlb_register_node
 static inline void hugetlb_unregister_node(struct node *node) {}

(Continue reading)

headers

Yasuaki Ishimatsu | 9 Jul 2012 12:35

[RFC PATCH v3 13/13] memory-hotplug : remove sysfs file of node

The patch adds node_set_offline() and unregister_one_node() to remove_memory()
for removing sysfs file of node.

CC: David Rientjes <rientjes <at> google.com>
CC: Jiang Liu <liuj97 <at> gmail.com>
CC: Len Brown <len.brown <at> intel.com>
CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
CC: Paul Mackerras <paulus <at> samba.org>
CC: Christoph Lameter <cl <at> linux.com>
Cc: Minchan Kim <minchan.kim <at> gmail.com>
CC: Andrew Morton <akpm <at> linux-foundation.org>
CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
CC: Wen Congyang <wency <at> cn.fujitsu.com>
Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>

---
 mm/memory_hotplug.c |    5 +++++
 1 file changed, 5 insertions(+)

Index: linux-3.5-rc4/mm/memory_hotplug.c
===================================================================
--- linux-3.5-rc4.orig/mm/memory_hotplug.c	2012-07-03 14:22:21.012982694 +0900
+++ linux-3.5-rc4/mm/memory_hotplug.c	2012-07-03 14:22:25.405925554 +0900
 <at>  <at>  -702,6 +702,11  <at>  <at>  int remove_memory(int nid, u64 start, u6
 	/* remove memmap entry */
 	firmware_map_remove(start, start + size - 1, "System RAM");

+	if (!node_present_pages(nid)) {
+		node_set_offline(nid);
+		unregister_one_node(nid);

(Continue reading)

headers

Yasuaki Ishimatsu | 9 Jul 2012 12:35

[RFC PATCH v3 13/13] memory-hotplug : remove sysfs file of node

The patch adds node_set_offline() and unregister_one_node() to remove_memory()
for removing sysfs file of node.

CC: David Rientjes <rientjes <at> google.com>
CC: Jiang Liu <liuj97 <at> gmail.com>
CC: Len Brown <len.brown <at> intel.com>
CC: Benjamin Herrenschmidt <benh <at> kernel.crashing.org>
CC: Paul Mackerras <paulus <at> samba.org>
CC: Christoph Lameter <cl <at> linux.com>
Cc: Minchan Kim <minchan.kim <at> gmail.com>
CC: Andrew Morton <akpm <at> linux-foundation.org>
CC: KOSAKI Motohiro <kosaki.motohiro <at> jp.fujitsu.com>
CC: Wen Congyang <wency <at> cn.fujitsu.com>
Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki <at> jp.fujitsu.com>

---
 mm/memory_hotplug.c |    5 +++++
 1 file changed, 5 insertions(+)

Index: linux-3.5-rc4/mm/memory_hotplug.c
===================================================================
--- linux-3.5-rc4.orig/mm/memory_hotplug.c	2012-07-03 14:22:21.012982694 +0900
+++ linux-3.5-rc4/mm/memory_hotplug.c	2012-07-03 14:22:25.405925554 +0900
 <at>  <at>  -702,6 +702,11  <at>  <at>  int remove_memory(int nid, u64 start, u6
 	/* remove memmap entry */
 	firmware_map_remove(start, start + size - 1, "System RAM");

+	if (!node_present_pages(nid)) {
+		node_set_offline(nid);
+		unregister_one_node(nid);

(Continue reading)

headers

Christoph Lameter | 9 Jul 2012 17:18

Re: [RFC PATCH v3 0/13] memory-hotplug : hot-remove physical memory

On Mon, 9 Jul 2012, Yasuaki Ishimatsu wrote:

> Even if you apply these patches, you cannot remove the physical memory
> completely since these patches are still under development. I want you to
> cooperate to improve the physical memory hot-remove. So please review these
> patches and give your comment/idea.

Could you at least give a method on how you want to do physical memory
removal? You would have to remove all objects from the range you want to
physically remove. That is only possible under special circumstances and
with a limited set of objects. Even if you exclusively use ZONE_MOVEABLE
you still may get cases where pages are pinned for a long time.

I am not sure that these patches are useful unless we know where you are
going with this. If we end up with a situation where we still cannot
remove physical memory then this patchset is not helpful.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo <at> kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont <at> kvack.org"> email <at> kvack.org </a>

headers

Yasuaki Ishimatsu | 10 Jul 2012 11:58

Re: [RFC PATCH v3 0/13] memory-hotplug : hot-remove physical memory

Hi Christoph,

2012/07/10 0:18, Christoph Lameter wrote:
>
> On Mon, 9 Jul 2012, Yasuaki Ishimatsu wrote:
>
>> Even if you apply these patches, you cannot remove the physical memory
>> completely since these patches are still under development. I want you to
>> cooperate to improve the physical memory hot-remove. So please review these
>> patches and give your comment/idea.
>
> Could you at least give a method on how you want to do physical memory
> removal?

We plan to release a dynamic hardware partitionable system. It will be
able to hot remove/add a system board which included memory and cpu.
But as you know, Linux does not support memory hot-remove on x86 box.
So I try to develop it.

Current plan to hot remove system board is to use container driver.
Thus I define the system board in ACPI DSDT table as a container device.
It have supported hot-add a container device. And if container device
has _EJ0 ACPI method, "eject" file to remove the container device is
prepared as follow:

# ls -l /sys/bus/acpi/devices/ACPI0004\:01/eject
--w-------. 1 root root 4096 Jul 10 18:19 /sys/bus/acpi/devices/ACPI0004:01/eject

When I hot-remove the container device, I echo 1 to the file as follow:

(Continue reading)

headers

Jiang Liu | 10 Jul 2012 18:50

Re: [RFC PATCH v3 0/13] memory-hotplug : hot-remove physical memory

On 07/10/2012 05:58 PM, Yasuaki Ishimatsu wrote:
> Hi Christoph,
> 
> 2012/07/10 0:18, Christoph Lameter wrote:
>>
>> On Mon, 9 Jul 2012, Yasuaki Ishimatsu wrote:
>>
>>> Even if you apply these patches, you cannot remove the physical memory
>>> completely since these patches are still under development. I want you to
>>> cooperate to improve the physical memory hot-remove. So please review these
>>> patches and give your comment/idea.
>>
>> Could you at least give a method on how you want to do physical memory
>> removal?
> 
> We plan to release a dynamic hardware partitionable system. It will be
> able to hot remove/add a system board which included memory and cpu.
> But as you know, Linux does not support memory hot-remove on x86 box.
> So I try to develop it.
> 
> Current plan to hot remove system board is to use container driver.
> Thus I define the system board in ACPI DSDT table as a container device.
> It have supported hot-add a container device. And if container device
> has _EJ0 ACPI method, "eject" file to remove the container device is
> prepared as follow:
> 
> # ls -l /sys/bus/acpi/devices/ACPI0004\:01/eject
> --w-------. 1 root root 4096 Jul 10 18:19 /sys/bus/acpi/devices/ACPI0004:01/eject
> 
> When I hot-remove the container device, I echo 1 to the file as follow:

(Continue reading)

headers

Yasuaki Ishimatsu | 11 Jul 2012 02:09

Re: [RFC PATCH v3 0/13] memory-hotplug : hot-remove physical memory

Hi Jiang,

2012/07/11 1:50, Jiang Liu wrote:
> On 07/10/2012 05:58 PM, Yasuaki Ishimatsu wrote:
>> Hi Christoph,
>>
>> 2012/07/10 0:18, Christoph Lameter wrote:
>>>
>>> On Mon, 9 Jul 2012, Yasuaki Ishimatsu wrote:
>>>
>>>> Even if you apply these patches, you cannot remove the physical memory
>>>> completely since these patches are still under development. I want you to
>>>> cooperate to improve the physical memory hot-remove. So please review these
>>>> patches and give your comment/idea.
>>>
>>> Could you at least give a method on how you want to do physical memory
>>> removal?
>>
>> We plan to release a dynamic hardware partitionable system. It will be
>> able to hot remove/add a system board which included memory and cpu.
>> But as you know, Linux does not support memory hot-remove on x86 box.
>> So I try to develop it.
>>
>> Current plan to hot remove system board is to use container driver.
>> Thus I define the system board in ACPI DSDT table as a container device.
>> It have supported hot-add a container device. And if container device
>> has _EJ0 ACPI method, "eject" file to remove the container device is
>> prepared as follow:
>>
>> # ls -l /sys/bus/acpi/devices/ACPI0004\:01/eject

(Continue reading)

headers

Jiang Liu | 11 Jul 2012 02:21

Re: [RFC PATCH v3 0/13] memory-hotplug : hot-remove physical memory

On 07/11/2012 08:09 AM, Yasuaki Ishimatsu wrote:
> Hi Jiang,
> 
> 2012/07/11 1:50, Jiang Liu wrote:
>> On 07/10/2012 05:58 PM, Yasuaki Ishimatsu wrote:
>>> Hi Christoph,
>>>
>>> 2012/07/10 0:18, Christoph Lameter wrote:
>>>>
>>>> On Mon, 9 Jul 2012, Yasuaki Ishimatsu wrote:
>>>>
>>>>> Even if you apply these patches, you cannot remove the physical memory
>>>>> completely since these patches are still under development. I want you to
>>>>> cooperate to improve the physical memory hot-remove. So please review these
>>>>> patches and give your comment/idea.
>>>>
>>>> Could you at least give a method on how you want to do physical memory
>>>> removal?
>>>
>>> We plan to release a dynamic hardware partitionable system. It will be
>>> able to hot remove/add a system board which included memory and cpu.
>>> But as you know, Linux does not support memory hot-remove on x86 box.
>>> So I try to develop it.
>>>
>>> Current plan to hot remove system board is to use container driver.
>>> Thus I define the system board in ACPI DSDT table as a container device.
>>> It have supported hot-add a container device. And if container device
>>> has _EJ0 ACPI method, "eject" file to remove the container device is
>>> prepared as follow:
>>>

(Continue reading)

headers

Yasuaki Ishimatsu | 11 Jul 2012 02:54

Re: [RFC PATCH v3 0/13] memory-hotplug : hot-remove physical memory

Hi Jiang,

2012/07/11 9:21, Jiang Liu wrote:
> On 07/11/2012 08:09 AM, Yasuaki Ishimatsu wrote:
>> Hi Jiang,
>>
>> 2012/07/11 1:50, Jiang Liu wrote:
>>> On 07/10/2012 05:58 PM, Yasuaki Ishimatsu wrote:
>>>> Hi Christoph,
>>>>
>>>> 2012/07/10 0:18, Christoph Lameter wrote:
>>>>>
>>>>> On Mon, 9 Jul 2012, Yasuaki Ishimatsu wrote:
>>>>>
>>>>>> Even if you apply these patches, you cannot remove the physical memory
>>>>>> completely since these patches are still under development. I want you to
>>>>>> cooperate to improve the physical memory hot-remove. So please review these
>>>>>> patches and give your comment/idea.
>>>>>
>>>>> Could you at least give a method on how you want to do physical memory
>>>>> removal?
>>>>
>>>> We plan to release a dynamic hardware partitionable system. It will be
>>>> able to hot remove/add a system board which included memory and cpu.
>>>> But as you know, Linux does not support memory hot-remove on x86 box.
>>>> So I try to develop it.
>>>>
>>>> Current plan to hot remove system board is to use container driver.
>>>> Thus I define the system board in ACPI DSDT table as a container device.
>>>> It have supported hot-add a container device. And if container device

(Continue reading)

headers

Jiang Liu | 11 Jul 2012 16:24

Re: [RFC PATCH v3 0/13] memory-hotplug : hot-remove physical memory

On 07/11/2012 08:54 AM, Yasuaki Ishimatsu wrote:
> Hi Jiang,
> 
> 2012/07/11 9:21, Jiang Liu wrote:
>> On 07/11/2012 08:09 AM, Yasuaki Ishimatsu wrote:
>>> Hi Jiang,
>>>
>>> 2012/07/11 1:50, Jiang Liu wrote:
>>>> On 07/10/2012 05:58 PM, Yasuaki Ishimatsu wrote:
>>>>> Hi Christoph,
>>>>>
>>>>> 2012/07/10 0:18, Christoph Lameter wrote:
>>>>>>
>>>>>> On Mon, 9 Jul 2012, Yasuaki Ishimatsu wrote:
>>>>>>
>>>>>>> Even if you apply these patches, you cannot remove the physical memory
>>>>>>> completely since these patches are still under development. I want you to
>>>>>>> cooperate to improve the physical memory hot-remove. So please review these
>>>>>>> patches and give your comment/idea.
>>>>>>
>>>>>> Could you at least give a method on how you want to do physical memory
>>>>>> removal?
>>>>>
>>>>> We plan to release a dynamic hardware partitionable system. It will be
>>>>> able to hot remove/add a system board which included memory and cpu.
>>>>> But as you know, Linux does not support memory hot-remove on x86 box.
>>>>> So I try to develop it.
>>>>>
>>>>> Current plan to hot remove system board is to use container driver.
>>>>> Thus I define the system board in ACPI DSDT table as a container device.

(Continue reading)

headers

Jiang Liu | 11 Jul 2012 16:24

Re: [RFC PATCH v3 0/13] memory-hotplug : hot-remove physical memory

On 07/11/2012 08:54 AM, Yasuaki Ishimatsu wrote:
> Hi Jiang,
> 
> 2012/07/11 9:21, Jiang Liu wrote:
>> On 07/11/2012 08:09 AM, Yasuaki Ishimatsu wrote:
>>> Hi Jiang,
>>>
>>> 2012/07/11 1:50, Jiang Liu wrote:
>>>> On 07/10/2012 05:58 PM, Yasuaki Ishimatsu wrote:
>>>>> Hi Christoph,
>>>>>
>>>>> 2012/07/10 0:18, Christoph Lameter wrote:
>>>>>>
>>>>>> On Mon, 9 Jul 2012, Yasuaki Ishimatsu wrote:
>>>>>>
>>>>>>> Even if you apply these patches, you cannot remove the physical memory
>>>>>>> completely since these patches are still under development. I want you to
>>>>>>> cooperate to improve the physical memory hot-remove. So please review these
>>>>>>> patches and give your comment/idea.
>>>>>>
>>>>>> Could you at least give a method on how you want to do physical memory
>>>>>> removal?
>>>>>
>>>>> We plan to release a dynamic hardware partitionable system. It will be
>>>>> able to hot remove/add a system board which included memory and cpu.
>>>>> But as you know, Linux does not support memory hot-remove on x86 box.
>>>>> So I try to develop it.
>>>>>
>>>>> Current plan to hot remove system board is to use container driver.
>>>>> Thus I define the system board in ACPI DSDT table as a container device.

(Continue reading)

headers

Yasuaki Ishimatsu | 11 Jul 2012 02:54

Re: [RFC PATCH v3 0/13] memory-hotplug : hot-remove physical memory

Hi Jiang,

2012/07/11 9:21, Jiang Liu wrote:
> On 07/11/2012 08:09 AM, Yasuaki Ishimatsu wrote:
>> Hi Jiang,
>>
>> 2012/07/11 1:50, Jiang Liu wrote:
>>> On 07/10/2012 05:58 PM, Yasuaki Ishimatsu wrote:
>>>> Hi Christoph,
>>>>
>>>> 2012/07/10 0:18, Christoph Lameter wrote:
>>>>>
>>>>> On Mon, 9 Jul 2012, Yasuaki Ishimatsu wrote:
>>>>>
>>>>>> Even if you apply these patches, you cannot remove the physical memory
>>>>>> completely since these patches are still under development. I want you to
>>>>>> cooperate to improve the physical memory hot-remove. So please review these
>>>>>> patches and give your comment/idea.
>>>>>
>>>>> Could you at least give a method on how you want to do physical memory
>>>>> removal?
>>>>
>>>> We plan to release a dynamic hardware partitionable system. It will be
>>>> able to hot remove/add a system board which included memory and cpu.
>>>> But as you know, Linux does not support memory hot-remove on x86 box.
>>>> So I try to develop it.
>>>>
>>>> Current plan to hot remove system board is to use container driver.
>>>> Thus I define the system board in ACPI DSDT table as a container device.
>>>> It have supported hot-add a container device. And if container device

(Continue reading)

headers

Jiang Liu | 11 Jul 2012 02:21

Re: [RFC PATCH v3 0/13] memory-hotplug : hot-remove physical memory

On 07/11/2012 08:09 AM, Yasuaki Ishimatsu wrote:
> Hi Jiang,
> 
> 2012/07/11 1:50, Jiang Liu wrote:
>> On 07/10/2012 05:58 PM, Yasuaki Ishimatsu wrote:
>>> Hi Christoph,
>>>
>>> 2012/07/10 0:18, Christoph Lameter wrote:
>>>>
>>>> On Mon, 9 Jul 2012, Yasuaki Ishimatsu wrote:
>>>>
>>>>> Even if you apply these patches, you cannot remove the physical memory
>>>>> completely since these patches are still under development. I want you to
>>>>> cooperate to improve the physical memory hot-remove. So please review these
>>>>> patches and give your comment/idea.
>>>>
>>>> Could you at least give a method on how you want to do physical memory
>>>> removal?
>>>
>>> We plan to release a dynamic hardware partitionable system. It will be
>>> able to hot remove/add a system board which included memory and cpu.
>>> But as you know, Linux does not support memory hot-remove on x86 box.
>>> So I try to develop it.
>>>
>>> Current plan to hot remove system board is to use container driver.
>>> Thus I define the system board in ACPI DSDT table as a container device.
>>> It have supported hot-add a container device. And if container device
>>> has _EJ0 ACPI method, "eject" file to remove the container device is
>>> prepared as follow:
>>>

(Continue reading)

headers

Yasuaki Ishimatsu | 11 Jul 2012 02:09

Re: [RFC PATCH v3 0/13] memory-hotplug : hot-remove physical memory

Hi Jiang,

2012/07/11 1:50, Jiang Liu wrote:
> On 07/10/2012 05:58 PM, Yasuaki Ishimatsu wrote:
>> Hi Christoph,
>>
>> 2012/07/10 0:18, Christoph Lameter wrote:
>>>
>>> On Mon, 9 Jul 2012, Yasuaki Ishimatsu wrote:
>>>
>>>> Even if you apply these patches, you cannot remove the physical memory
>>>> completely since these patches are still under development. I want you to
>>>> cooperate to improve the physical memory hot-remove. So please review these
>>>> patches and give your comment/idea.
>>>
>>> Could you at least give a method on how you want to do physical memory
>>> removal?
>>
>> We plan to release a dynamic hardware partitionable system. It will be
>> able to hot remove/add a system board which included memory and cpu.
>> But as you know, Linux does not support memory hot-remove on x86 box.
>> So I try to develop it.
>>
>> Current plan to hot remove system board is to use container driver.
>> Thus I define the system board in ACPI DSDT table as a container device.
>> It have supported hot-add a container device. And if container device
>> has _EJ0 ACPI method, "eject" file to remove the container device is
>> prepared as follow:
>>
>> # ls -l /sys/bus/acpi/devices/ACPI0004\:01/eject

(Continue reading)

headers

Jiang Liu | 10 Jul 2012 18:50

Re: [RFC PATCH v3 0/13] memory-hotplug : hot-remove physical memory

On 07/10/2012 05:58 PM, Yasuaki Ishimatsu wrote:
> Hi Christoph,
> 
> 2012/07/10 0:18, Christoph Lameter wrote:
>>
>> On Mon, 9 Jul 2012, Yasuaki Ishimatsu wrote:
>>
>>> Even if you apply these patches, you cannot remove the physical memory
>>> completely since these patches are still under development. I want you to
>>> cooperate to improve the physical memory hot-remove. So please review these
>>> patches and give your comment/idea.
>>
>> Could you at least give a method on how you want to do physical memory
>> removal?
> 
> We plan to release a dynamic hardware partitionable system. It will be
> able to hot remove/add a system board which included memory and cpu.
> But as you know, Linux does not support memory hot-remove on x86 box.
> So I try to develop it.
> 
> Current plan to hot remove system board is to use container driver.
> Thus I define the system board in ACPI DSDT table as a container device.
> It have supported hot-add a container device. And if container device
> has _EJ0 ACPI method, "eject" file to remove the container device is
> prepared as follow:
> 
> # ls -l /sys/bus/acpi/devices/ACPI0004\:01/eject
> --w-------. 1 root root 4096 Jul 10 18:19 /sys/bus/acpi/devices/ACPI0004:01/eject
> 
> When I hot-remove the container device, I echo 1 to the file as follow:

(Continue reading)

headers

Yasuaki Ishimatsu | 10 Jul 2012 11:58

Re: [RFC PATCH v3 0/13] memory-hotplug : hot-remove physical memory

Hi Christoph,

2012/07/10 0:18, Christoph Lameter wrote:
>
> On Mon, 9 Jul 2012, Yasuaki Ishimatsu wrote:
>
>> Even if you apply these patches, you cannot remove the physical memory
>> completely since these patches are still under development. I want you to
>> cooperate to improve the physical memory hot-remove. So please review these
>> patches and give your comment/idea.
>
> Could you at least give a method on how you want to do physical memory
> removal?

We plan to release a dynamic hardware partitionable system. It will be
able to hot remove/add a system board which included memory and cpu.
But as you know, Linux does not support memory hot-remove on x86 box.
So I try to develop it.

Current plan to hot remove system board is to use container driver.
Thus I define the system board in ACPI DSDT table as a container device.
It have supported hot-add a container device. And if container device
has _EJ0 ACPI method, "eject" file to remove the container device is
prepared as follow:

# ls -l /sys/bus/acpi/devices/ACPI0004\:01/eject
--w-------. 1 root root 4096 Jul 10 18:19 /sys/bus/acpi/devices/ACPI0004:01/eject

When I hot-remove the container device, I echo 1 to the file as follow:

(Continue reading)

headers

Christoph Lameter | 9 Jul 2012 17:18

Re: [RFC PATCH v3 0/13] memory-hotplug : hot-remove physical memory

On Mon, 9 Jul 2012, Yasuaki Ishimatsu wrote:

> Even if you apply these patches, you cannot remove the physical memory
> completely since these patches are still under development. I want you to
> cooperate to improve the physical memory hot-remove. So please review these
> patches and give your comment/idea.

Could you at least give a method on how you want to do physical memory
removal? You would have to remove all objects from the range you want to
physically remove. That is only possible under special circumstances and
with a limited set of objects. Even if you exclusively use ZONE_MOVEABLE
you still may get cases where pages are pinned for a long time.

I am not sure that these patches are useful unless we know where you are
going with this. If we end up with a situation where we still cannot
remove physical memory then this patchset is not helpful.

headers

Wen Congyang | 11 Jul 2012 03:52

Re: [RFC PATCH v3 0/13] memory-hotplug : hot-remove physical memory

At 07/09/2012 06:21 PM, Yasuaki Ishimatsu Wrote:
> This patch series aims to support physical memory hot-remove.
> 
>   [RFC PATCH v3 1/13] memory-hotplug : rename remove_memory to offline_memory
>   [RFC PATCH v3 2/13] memory-hotplug : add physical memory hotplug code to acpi_memory_device_remove
>   [RFC PATCH v3 3/13] memory-hotplug : unify argument of firmware_map_add_early/hotplug
>   [RFC PATCH v3 4/13] memory-hotplug : remove /sys/firmware/memmap/X sysfs
>   [RFC PATCH v3 5/13] memory-hotplug : does not release memory region in PAGES_PER_SECTION chunks
>   [RFC PATCH v3 6/13] memory-hotplug : add memory_block_release
>   [RFC PATCH v3 7/13] memory-hotplug : remove_memory calls __remove_pages
>   [RFC PATCH v3 8/13] memory-hotplug : check page type in get_page_bootmem
>   [RFC PATCH v3 9/13] memory-hotplug : move register_page_bootmem_info_node and put_page_bootmem for
> sparse-vmemmap
>   [RFC PATCH v3 10/13] memory-hotplug : implement register_page_bootmem_info_section of sparse-vmemmap
>   [RFC PATCH v3 11/13] memory-hotplug : free memmap of sparse-vmemmap
>   [RFC PATCH v3 12/13] memory-hotplug : add node_device_release
>   [RFC PATCH v3 13/13] memory-hotplug : remove sysfs file of node
> 
> Even if you apply these patches, you cannot remove the physical memory
> completely since these patches are still under development. I want you to
> cooperate to improve the physical memory hot-remove. So please review these
> patches and give your comment/idea.
> 
> The patches can free/remove following things:
> 
>   - acpi_memory_info                          : [RFC PATCH 2/13]
>   - /sys/firmware/memmap/X/{end, start, type} : [RFC PATCH 4/13]
>   - iomem_resource                            : [RFC PATCH 5/13]
>   - mem_section and related sysfs files       : [RFC PATCH 6-11/13]
>   - node and related sysfs files              : [RFC PATCH 12-13/13]

(Continue reading)

headers

Wen Congyang | 11 Jul 2012 04:24

Re: [RFC PATCH v3 0/13] memory-hotplug : hot-remove physical memory

At 07/11/2012 09:52 AM, Wen Congyang Wrote:
> At 07/09/2012 06:21 PM, Yasuaki Ishimatsu Wrote:
>> This patch series aims to support physical memory hot-remove.
>>
>>   [RFC PATCH v3 1/13] memory-hotplug : rename remove_memory to offline_memory
>>   [RFC PATCH v3 2/13] memory-hotplug : add physical memory hotplug code to acpi_memory_device_remove
>>   [RFC PATCH v3 3/13] memory-hotplug : unify argument of firmware_map_add_early/hotplug
>>   [RFC PATCH v3 4/13] memory-hotplug : remove /sys/firmware/memmap/X sysfs
>>   [RFC PATCH v3 5/13] memory-hotplug : does not release memory region in PAGES_PER_SECTION chunks
>>   [RFC PATCH v3 6/13] memory-hotplug : add memory_block_release
>>   [RFC PATCH v3 7/13] memory-hotplug : remove_memory calls __remove_pages
>>   [RFC PATCH v3 8/13] memory-hotplug : check page type in get_page_bootmem
>>   [RFC PATCH v3 9/13] memory-hotplug : move register_page_bootmem_info_node and put_page_bootmem for
>> sparse-vmemmap
>>   [RFC PATCH v3 10/13] memory-hotplug : implement register_page_bootmem_info_section of sparse-vmemmap
>>   [RFC PATCH v3 11/13] memory-hotplug : free memmap of sparse-vmemmap
>>   [RFC PATCH v3 12/13] memory-hotplug : add node_device_release
>>   [RFC PATCH v3 13/13] memory-hotplug : remove sysfs file of node
>>
>> Even if you apply these patches, you cannot remove the physical memory
>> completely since these patches are still under development. I want you to
>> cooperate to improve the physical memory hot-remove. So please review these
>> patches and give your comment/idea.
>>
>> The patches can free/remove following things:
>>
>>   - acpi_memory_info                          : [RFC PATCH 2/13]
>>   - /sys/firmware/memmap/X/{end, start, type} : [RFC PATCH 4/13]
>>   - iomem_resource                            : [RFC PATCH 5/13]
>>   - mem_section and related sysfs files       : [RFC PATCH 6-11/13]

(Continue reading)

headers

Wen Congyang | 11 Jul 2012 04:24

Re: [RFC PATCH v3 0/13] memory-hotplug : hot-remove physical memory

At 07/11/2012 09:52 AM, Wen Congyang Wrote:
> At 07/09/2012 06:21 PM, Yasuaki Ishimatsu Wrote:
>> This patch series aims to support physical memory hot-remove.
>>
>>   [RFC PATCH v3 1/13] memory-hotplug : rename remove_memory to offline_memory
>>   [RFC PATCH v3 2/13] memory-hotplug : add physical memory hotplug code to acpi_memory_device_remove
>>   [RFC PATCH v3 3/13] memory-hotplug : unify argument of firmware_map_add_early/hotplug
>>   [RFC PATCH v3 4/13] memory-hotplug : remove /sys/firmware/memmap/X sysfs
>>   [RFC PATCH v3 5/13] memory-hotplug : does not release memory region in PAGES_PER_SECTION chunks
>>   [RFC PATCH v3 6/13] memory-hotplug : add memory_block_release
>>   [RFC PATCH v3 7/13] memory-hotplug : remove_memory calls __remove_pages
>>   [RFC PATCH v3 8/13] memory-hotplug : check page type in get_page_bootmem
>>   [RFC PATCH v3 9/13] memory-hotplug : move register_page_bootmem_info_node and put_page_bootmem for
>> sparse-vmemmap
>>   [RFC PATCH v3 10/13] memory-hotplug : implement register_page_bootmem_info_section of sparse-vmemmap
>>   [RFC PATCH v3 11/13] memory-hotplug : free memmap of sparse-vmemmap
>>   [RFC PATCH v3 12/13] memory-hotplug : add node_device_release
>>   [RFC PATCH v3 13/13] memory-hotplug : remove sysfs file of node
>>
>> Even if you apply these patches, you cannot remove the physical memory
>> completely since these patches are still under development. I want you to
>> cooperate to improve the physical memory hot-remove. So please review these
>> patches and give your comment/idea.
>>
>> The patches can free/remove following things:
>>
>>   - acpi_memory_info                          : [RFC PATCH 2/13]
>>   - /sys/firmware/memmap/X/{end, start, type} : [RFC PATCH 4/13]
>>   - iomem_resource                            : [RFC PATCH 5/13]
>>   - mem_section and related sysfs files       : [RFC PATCH 6-11/13]

(Continue reading)

headers

Wen Congyang | 11 Jul 2012 03:52

Re: [RFC PATCH v3 0/13] memory-hotplug : hot-remove physical memory

At 07/09/2012 06:21 PM, Yasuaki Ishimatsu Wrote:
> This patch series aims to support physical memory hot-remove.
> 
>   [RFC PATCH v3 1/13] memory-hotplug : rename remove_memory to offline_memory
>   [RFC PATCH v3 2/13] memory-hotplug : add physical memory hotplug code to acpi_memory_device_remove
>   [RFC PATCH v3 3/13] memory-hotplug : unify argument of firmware_map_add_early/hotplug
>   [RFC PATCH v3 4/13] memory-hotplug : remove /sys/firmware/memmap/X sysfs
>   [RFC PATCH v3 5/13] memory-hotplug : does not release memory region in PAGES_PER_SECTION chunks
>   [RFC PATCH v3 6/13] memory-hotplug : add memory_block_release
>   [RFC PATCH v3 7/13] memory-hotplug : remove_memory calls __remove_pages
>   [RFC PATCH v3 8/13] memory-hotplug : check page type in get_page_bootmem
>   [RFC PATCH v3 9/13] memory-hotplug : move register_page_bootmem_info_node and put_page_bootmem for
> sparse-vmemmap
>   [RFC PATCH v3 10/13] memory-hotplug : implement register_page_bootmem_info_section of sparse-vmemmap
>   [RFC PATCH v3 11/13] memory-hotplug : free memmap of sparse-vmemmap
>   [RFC PATCH v3 12/13] memory-hotplug : add node_device_release
>   [RFC PATCH v3 13/13] memory-hotplug : remove sysfs file of node
> 
> Even if you apply these patches, you cannot remove the physical memory
> completely since these patches are still under development. I want you to
> cooperate to improve the physical memory hot-remove. So please review these
> patches and give your comment/idea.
> 
> The patches can free/remove following things:
> 
>   - acpi_memory_info                          : [RFC PATCH 2/13]
>   - /sys/firmware/memmap/X/{end, start, type} : [RFC PATCH 4/13]
>   - iomem_resource                            : [RFC PATCH 5/13]
>   - mem_section and related sysfs files       : [RFC PATCH 6-11/13]
>   - node and related sysfs files              : [RFC PATCH 12-13/13]

(Continue reading)