diff options
author | Wen Congyang <wency@cn.fujitsu.com> | 2012-10-08 16:34:01 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2012-10-09 16:23:02 +0900 |
commit | e90bdb7f52f94204c78fb40b0804645defdebd71 (patch) | |
tree | 4acb09ecd1f98fd98408f18e816d075601585d2a /mm/huge_memory.c | |
parent | a16cee10c7ab994546ed98d9abfd4de74050124a (diff) | |
download | talos-obmc-linux-e90bdb7f52f94204c78fb40b0804645defdebd71.tar.gz talos-obmc-linux-e90bdb7f52f94204c78fb40b0804645defdebd71.zip |
memory-hotplug: update memory block's state and notify userspace
remove_memory() will be called when hot removing a memory device. But
even if offlining memory, we cannot notice it. So the patch updates the
memory block's state and sends notification to userspace.
Additionally, the memory device may contain more than one memory block.
If the memory block has been offlined, __offline_pages() will fail. So we
should try to offline one memory block at a time.
Thus remove_memory() also check each memory block's state. So there is no
need to check the memory block's state before calling remove_memory().
Signed-off-by: Wen Congyang <wency@cn.fujitsu.com>
Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
Cc: David Rientjes <rientjes@google.com>
Cc: Jiang Liu <liuj97@gmail.com>
Cc: Len Brown <len.brown@intel.com>
Cc: Christoph Lameter <cl@linux.com>
Cc: Minchan Kim <minchan.kim@gmail.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'mm/huge_memory.c')
0 files changed, 0 insertions, 0 deletions