Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933208Ab2JTAox (ORCPT ); Fri, 19 Oct 2012 20:44:53 -0400 Received: from cn.fujitsu.com ([222.73.24.84]:65294 "EHLO song.cn.fujitsu.com" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1755233Ab2JTAov (ORCPT ); Fri, 19 Oct 2012 20:44:51 -0400 X-IronPort-AV: E=Sophos;i="4.80,617,1344182400"; d="scan'208";a="6033354" Message-ID: <5081F552.9060008@cn.fujitsu.com> Date: Sat, 20 Oct 2012 08:50:26 +0800 From: Wen Congyang User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100413 Fedora/3.0.4-2.fc13 Thunderbird/3.0.4 MIME-Version: 1.0 To: "Rafael J. Wysocki" CC: linux-mm@kvack.org, linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org, liuj97@gmail.com, len.brown@intel.com, akpm@linux-foundation.org, kosaki.motohiro@jp.fujitsu.com, isimatu.yasuaki@jp.fujitsu.com, muneda.takahiro@jp.fujitsu.com Subject: Re: [PATCH v2 0/3] acpi,memory-hotplug : implement framework for hot removing memory References: <1350641040-19434-1-git-send-email-wency@cn.fujitsu.com> <10485269.ao9A69hu9S@vostro.rjw.lan> In-Reply-To: <10485269.ao9A69hu9S@vostro.rjw.lan> X-MIMETrack: Itemize by SMTP Server on mailserver/fnst(Release 8.5.3|September 15, 2011) at 2012/10/20 08:44:23, Serialize by Router on mailserver/fnst(Release 8.5.3|September 15, 2011) at 2012/10/20 08:44:24, Serialize complete at 2012/10/20 08:44:24 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2318 Lines: 66 At 10/20/2012 12:32 AM, Rafael J. Wysocki Wrote: > On Friday 19 of October 2012 18:03:57 wency@cn.fujitsu.com wrote: >> From: Wen Congyang >> >> 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? Current Linux's tree. Thanks Wen Congyang > > Thanks, > Rafael > > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/