Commit 5fc1d66a authored by Tang Chen's avatar Tang Chen Committed by Linus Torvalds
Browse files

memory-hotplug: integrated __remove_section() of CONFIG_SPARSEMEM_VMEMMAP.

Currently __remove_section for SPARSEMEM_VMEMMAP does nothing.  But even
if we use SPARSEMEM_VMEMMAP, we can unregister the memory_section.
Signed-off-by: default avatarYasuaki Ishimatsu <>
Signed-off-by: default avatarWen Congyang <>
Signed-off-by: default avatarTang Chen <>
Cc: KOSAKI Motohiro <>
Cc: Jiang Liu <>
Cc: Jianguo Wu <>
Cc: Kamezawa Hiroyuki <>
Cc: Lai Jiangshan <>
Cc: Wu Jianguo <>
Cc: Ingo Molnar <>
Cc: Thomas Gleixner <>
Cc: "H. Peter Anvin" <>
Signed-off-by: default avatarAndrew Morton <>
Signed-off-by: default avatarLinus Torvalds <>
parent 0197518c
......@@ -432,16 +432,6 @@ static int __meminit __add_section(int nid, struct zone *zone,
return register_new_memory(nid, __pfn_to_section(phys_start_pfn));
static int __remove_section(struct zone *zone, struct mem_section *ms)
* XXX: Freeing memmap with vmemmap is not implement yet.
* This should be removed later.
return -EBUSY;
static int __remove_section(struct zone *zone, struct mem_section *ms)
int ret = -EINVAL;
......@@ -456,7 +446,6 @@ static int __remove_section(struct zone *zone, struct mem_section *ms)
sparse_remove_one_section(zone, ms);
return 0;
* Reasonably generic function for adding memory. It is
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment