From: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
To: wency@cn.fujitsu.com
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, muneda.takahiro@jp.fujitsu.com,
rjw@sisk.pl
Subject: Re: [PATCH v2 0/3] acpi,memory-hotplug : implement framework for hot removing memory
Date: Fri, 19 Oct 2012 19:19:53 +0900 [thread overview]
Message-ID: <50812949.6040005@jp.fujitsu.com> (raw)
In-Reply-To: <1350641040-19434-1-git-send-email-wency@cn.fujitsu.com>
CCing Rafael, because he become ACPI Maintainer.
Hi Wen,
If you update the patch-set, please CCing Rafael from the next time.
Thanks,
Yasuaki Ishimatsu
2012/10/19 19:03, wency@cn.fujitsu.com wrote:
> From: Wen Congyang <wency@cn.fujitsu.com>
>
> 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(-)
>
WARNING: multiple messages have this Message-ID (diff)
From: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
To: wency@cn.fujitsu.com
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, muneda.takahiro@jp.fujitsu.com,
rjw@sisk.pl
Subject: Re: [PATCH v2 0/3] acpi,memory-hotplug : implement framework for hot removing memory
Date: Fri, 19 Oct 2012 19:19:53 +0900 [thread overview]
Message-ID: <50812949.6040005@jp.fujitsu.com> (raw)
In-Reply-To: <1350641040-19434-1-git-send-email-wency@cn.fujitsu.com>
CCing Rafael, because he become ACPI Maintainer.
Hi Wen,
If you update the patch-set, please CCing Rafael from the next time.
Thanks,
Yasuaki Ishimatsu
2012/10/19 19:03, wency@cn.fujitsu.com wrote:
> From: Wen Congyang <wency@cn.fujitsu.com>
>
> 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(-)
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
To: <wency@cn.fujitsu.com>
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>,
<muneda.takahiro@jp.fujitsu.com>, <rjw@sisk.pl>
Subject: Re: [PATCH v2 0/3] acpi,memory-hotplug : implement framework for hot removing memory
Date: Fri, 19 Oct 2012 19:19:53 +0900 [thread overview]
Message-ID: <50812949.6040005@jp.fujitsu.com> (raw)
In-Reply-To: <1350641040-19434-1-git-send-email-wency@cn.fujitsu.com>
CCing Rafael, because he become ACPI Maintainer.
Hi Wen,
If you update the patch-set, please CCing Rafael from the next time.
Thanks,
Yasuaki Ishimatsu
2012/10/19 19:03, wency@cn.fujitsu.com wrote:
> From: Wen Congyang <wency@cn.fujitsu.com>
>
> 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(-)
>
next prev parent reply other threads:[~2012-10-19 10:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-19 10:03 [PATCH v2 0/3] acpi,memory-hotplug : implement framework for hot removing memory wency
2012-10-19 10:03 ` wency
2012-10-19 10:03 ` [PATCH v2 1/3] acpi,memory-hotplug: call acpi_bus_trim() to remove memory device wency
2012-10-19 10:03 ` wency
2012-10-19 18:26 ` KOSAKI Motohiro
2012-10-19 18:26 ` KOSAKI Motohiro
2012-10-19 10:03 ` [PATCH v2 2/3] acpi,memory-hotplug: introduce a mutex lock to protect the list in acpi_memory_device wency
2012-10-19 10:03 ` wency
2012-10-19 19:20 ` KOSAKI Motohiro
2012-10-19 19:20 ` KOSAKI Motohiro
2012-10-19 10:04 ` [PATCH v2 3/3] acpi,memory-hotplug : add memory offline code to acpi_memory_device_remove() wency
2012-10-19 10:04 ` wency
2012-10-19 10:19 ` Yasuaki Ishimatsu [this message]
2012-10-19 10:19 ` [PATCH v2 0/3] acpi,memory-hotplug : implement framework for hot removing memory Yasuaki Ishimatsu
2012-10-19 10:19 ` Yasuaki Ishimatsu
2012-10-19 10:40 ` Wen Congyang
2012-10-19 10:40 ` Wen Congyang
2012-10-19 16:32 ` Rafael J. Wysocki
2012-10-19 16:32 ` Rafael J. Wysocki
2012-10-20 0:50 ` Wen Congyang
2012-10-20 0:50 ` Wen Congyang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50812949.6040005@jp.fujitsu.com \
--to=isimatu.yasuaki@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuj97@gmail.com \
--cc=muneda.takahiro@jp.fujitsu.com \
--cc=rjw@sisk.pl \
--cc=wency@cn.fujitsu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.