summaryrefslogtreecommitdiff
path: root/mm/msync.c
diff options
context:
space:
mode:
authorRafael J. Wysocki <rafael.j.wysocki@intel.com>2013-05-08 02:29:49 +0400
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2013-05-12 16:14:38 +0400
commite2ff39400d81233374e780b133496a2296643d7d (patch)
tree6f96f82ebc9474652a32e7fff8f8d9eb7184eb56 /mm/msync.c
parentac212b6980d8d5eda705864fc5a8ecddc6d6eacc (diff)
downloadlinux-e2ff39400d81233374e780b133496a2296643d7d.tar.xz
ACPI / memhotplug: Bind removable memory blocks to ACPI device nodes
During ACPI memory hotplug configuration bind memory blocks residing in modules removable through the standard ACPI mechanism to struct acpi_device objects associated with ACPI namespace objects representing those modules. Accordingly, unbind those memory blocks from the struct acpi_device objects when the memory modules in question are being removed. When "offline" operation for devices representing memory blocks is introduced, this will allow the ACPI core's device hot-remove code to use it to carry out remove_memory() for those memory blocks and check the results of that before it actually removes the modules holding them from the system. Since walk_memory_range() is used for accessing all memory blocks corresponding to a given ACPI namespace object, it is exported from memory_hotplug.c so that the code in acpi_memhotplug.c can use it. Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Tested-by: Vasilis Liaskovitis <vasilis.liaskovitis@profitbricks.com> Reviewed-by: Toshi Kani <toshi.kani@hp.com>
Diffstat (limited to 'mm/msync.c')
0 files changed, 0 insertions, 0 deletions