|| ||Wen Congyang <email@example.com> |
|| ||firstname.lastname@example.org, email@example.com,
firstname.lastname@example.org, Len Brown <email@example.com>,
"Rafael J. Wysocki" <firstname.lastname@example.org> |
|| ||[Patch v5 0/7] acpi,memory-hotplug: implement framework for hot removing memory |
|| ||Thu, 15 Nov 2012 14:59:30 +0800|
|| ||Andrew Morton <email@example.com>,
Yasuaki Ishimatsu <firstname.lastname@example.org>,
Lai Jiangshan <email@example.com>,
Jiang Liu <firstname.lastname@example.org>,
KOSAKI Motohiro <email@example.com>,
Minchan Kim <firstname.lastname@example.org>,
Mel Gorman <email@example.com>,
David Rientjes <firstname.lastname@example.org>,
Konrad Rzeszutek Wilk <email@example.com>,
Toshi Kani <firstname.lastname@example.org>,
Wen Congyang <email@example.com>|
|| ||Article, Thread
The memory device can be removed by 2 ways:
1. send eject request by SCI
2. echo 1 >/sys/bus/pci/devices/PNP0C80:XX/eject
In the 1st case, acpi_memory_disable_device() will be called.
In the 2nd case, acpi_memory_device_remove() will be called.
acpi_memory_device_remove() will also be called when we unbind the
memory device from the driver acpi_memhotplug or a driver initialization
acpi_memory_disable_device() has already implemented a code which
offlines memory and releases acpi_memory_info struct . But
acpi_memory_device_remove() has not implemented it yet.
So the patch prepares the framework for hot removing memory and
adds the framework into acpi_memory_device_remove().
We may hotremove the memory device by this 2 ways at the same time.
So we remove the function acpi_memory_disable_device(), and use
acpi_bus_hot_remove_device() which is used by 2nd case to implement it.
We lock device in acpi_bus_hot_remove_device(), so there is no
need to add lock in acpi_memhotplug.
The last version of this patchset is here:
1. The following commit in pm tree can be dropped now(The other two patches
are already dropped):
2. This patchset requires the following patch(It is in pm tree now)
Changes from v4 to v5:
1. patch2: new patch. use acpi_bus_hot_remove_device() to implement memory
Changes from v3 to v4:
1. patch1: unlock list_lock when removing memory fails.
2. patch2: just rebase them
3. patch3-7: these patches are in -mm tree, and they conflict with this
patchset, so Adrew Morton drop them from -mm tree. I rebase and merge
them into this patchset.
Wen Congyang (6):
acpi,memory-hotplug: deal with eject request in hotplug queue
acpi_memhotplug.c: fix memory leak when memory device is unbound from
the module acpi_memhotplug
acpi_memhotplug.c: free memory device if acpi_memory_enable_device()
acpi_memhotplug.c: don't allow to eject the memory device if it is
acpi_memhotplug.c: bind the memory device when the driver is being
acpi_memhotplug.c: auto bind the memory device which is hotplugged
before the driver is loaded
Yasuaki Ishimatsu (1):
acpi,memory-hotplug : add memory offline code to
drivers/acpi/acpi_memhotplug.c | 206 ++++++++++++++++++++++-------------------
1 file changed, 109 insertions(+), 97 deletions(-)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/