aboutsummaryrefslogtreecommitdiffstats
path: root/REPORTING-BUGS
diff options
context:
space:
mode:
authorSeth Jennings <sjenning@linux.vnet.ibm.com>2013-08-20 16:05:05 -0500
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2013-08-21 11:52:20 -0700
commitfa2be40fe7c0aa3b7accbf6dfa9ef0976e191d4c (patch)
treea51ae32d86315a68029a65fe028a2ade240050df /REPORTING-BUGS
parentdrivers: base: refactor add_memory_section() to add_memory_block() (diff)
downloadlinux-dev-fa2be40fe7c0aa3b7accbf6dfa9ef0976e191d4c.tar.xz
linux-dev-fa2be40fe7c0aa3b7accbf6dfa9ef0976e191d4c.zip
drivers: base: use standard device online/offline for state change
There are two ways to set the online/offline state for a memory block: echo 0|1 > online and echo online|online_kernel|online_movable|offline > state. The state attribute can online a memory block with extra data, the "online type", where the online attribute uses a default online type of ONLINE_KEEP, same as echo online > state. Currently there is a state_mutex that provides consistency between the memory block state and the underlying memory. The problem is that this code does a lot of things that the common device layer can do for us, such as the serialization of the online/offline handlers using the device lock, setting the dev->offline field, and calling kobject_uevent(). This patch refactors the online/offline code to allow the common device_[online|offline] functions to be used. The result is a simpler and more common code path for the two state setting mechanisms. It also removes the state_mutex from the struct memory_block as the memory block device lock provides the state consistency. No functional change is intended by this patch. Signed-off-by: Seth Jennings <sjenning@linux.vnet.ibm.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'REPORTING-BUGS')
0 files changed, 0 insertions, 0 deletions