diff options
author | Nathan Fontenot <nfont@linux.vnet.ibm.com> | 2017-02-24 15:00:02 -0800 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2017-02-24 17:46:56 -0800 |
commit | dc18d706a4367454ad1fc51e06148d54e8ecfaa0 (patch) | |
tree | c72bb090e93017548b6f50537883e151caf87ac4 /lib/ioremap.c | |
parent | dd8416c47715cf324c9a16f13273f9fda87acfed (diff) | |
download | linux-stable-dc18d706a4367454ad1fc51e06148d54e8ecfaa0.tar.gz linux-stable-dc18d706a4367454ad1fc51e06148d54e8ecfaa0.tar.bz2 linux-stable-dc18d706a4367454ad1fc51e06148d54e8ecfaa0.zip |
memory-hotplug: use dev_online for memhp_auto_online
Commit 31bc3858ea3e ("add automatic onlining policy for the newly added
memory") provides the capability to have added memory automatically
onlined during add, but this appears to be slightly broken.
The current implementation uses walk_memory_range() to call
online_memory_block, which uses memory_block_change_state() to online
the memory. Instead, we should be calling device_online() for the
memory block in online_memory_block(). This would online the memory
(the memory bus online routine memory_subsys_online() called from
device_online calls memory_block_change_state()) and properly update the
device struct offline flag.
As a result of the current implementation, attempting to remove a memory
block after adding it using auto online fails. This is because doing a
remove, for instance
echo offline > /sys/devices/system/memory/memoryXXX/state
uses device_offline() which checks the dev->offline flag.
Link: http://lkml.kernel.org/r/20170222220744.8119.19687.stgit@ltcalpine2-lp14.aus.stglabs.ibm.com
Signed-off-by: Nathan Fontenot <nfont@linux.vnet.ibm.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>
Cc: Michael Roth <mdroth@linux.vnet.ibm.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'lib/ioremap.c')
0 files changed, 0 insertions, 0 deletions