On Friday 19 of October 2012 18:03:57 wency@xxxxxxxxxxxxxx wrote: > From: Wen Congyang <wency@xxxxxxxxxxxxxx> > > The patch-set implements a framework for hot removing memory. > > 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 > fails. > > 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(). > > The last version of this patchset is here: > https://lkml.org/lkml/2012/10/3/126 > > Changelos from v1 to v2: > Patch1: use acpi_bus_trim() instead of acpi_bus_remove() > Patch2: new patch, introduce a lock to protect the list > Patch3: remove memory too when type is ACPI_BUS_REMOVAL_NORMAL > Note: I don't send [Patch2-4 v1] in this series because they > are no logical changes in these 3 patches. > > Wen Congyang (2): > acpi,memory-hotplug: call acpi_bus_trim() to remove memory device > acpi,memory-hotplug: introduce a mutex lock to protect the list in > acpi_memory_device > > Yasuaki Ishimatsu (1): > acpi,memory-hotplug : add memory offline code to > acpi_memory_device_remove() > > drivers/acpi/acpi_memhotplug.c | 51 ++++++++++++++++++++++++++++++++-------- > 1 files changed, 41 insertions(+), 10 deletions(-) > > -- Can you please tell me what kernel is the series supposed to apply to? Is it the current Linus' tree, or linux-next, or something else? Thanks, Rafael -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
