From: wency@cn.fujitsu.com
To: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-acpi@vger.kernel.org,
linux-s390@vger.kernel.org, linux-sh@vger.kernel.org,
linux-ia64@vger.kernel.org, cmetcalf@tilera.com
Cc: rientjes@google.com, liuj97@gmail.com, len.brown@intel.com,
benh@kernel.crashing.org, paulus@samba.org, cl@linux.com,
minchan.kim@gmail.com, akpm@linux-foundation.org,
kosaki.motohiro@jp.fujitsu.com, isimatu.yasuaki@jp.fujitsu.com,
Wen Congyang <wency@cn.fujitsu.com>
Subject: [RFC V7 PATCH 07/19] memory-hotplug: call acpi_bus_remove() to remove memory device
Date: Mon, 20 Aug 2012 17:35:30 +0800 [thread overview]
Message-ID: <1345455342-27752-8-git-send-email-wency@cn.fujitsu.com> (raw)
In-Reply-To: <1345455342-27752-1-git-send-email-wency@cn.fujitsu.com>
From: Wen Congyang <wency@cn.fujitsu.com>
The memory device has been ejected and powoffed, so we can call
acpi_bus_remove() to remove the memory device from acpi bus.
CC: David Rientjes <rientjes@google.com>
CC: Jiang Liu <liuj97@gmail.com>
CC: Len Brown <len.brown@intel.com>
CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
CC: Paul Mackerras <paulus@samba.org>
CC: Christoph Lameter <cl@linux.com>
Cc: Minchan Kim <minchan.kim@gmail.com>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
CC: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
Signed-off-by: Wen Congyang <wency@cn.fujitsu.com>
---
drivers/acpi/acpi_memhotplug.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/drivers/acpi/acpi_memhotplug.c b/drivers/acpi/acpi_memhotplug.c
index 9d47458..b152767 100644
--- a/drivers/acpi/acpi_memhotplug.c
+++ b/drivers/acpi/acpi_memhotplug.c
@@ -425,8 +425,9 @@ static void acpi_memory_device_notify(acpi_handle handle, u32 event, void *data)
}
/*
- * TBD: Invoke acpi_bus_remove to cleanup data structures
+ * Invoke acpi_bus_remove() to remove memory device
*/
+ acpi_bus_remove(device, 1);
/* _EJ0 succeeded; _OST is not necessary */
return;
--
1.7.1
next prev parent reply other threads:[~2012-08-20 9:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 9:35 [RFC V7 PATCH 00/19] memory-hotplug: hot-remove physical memory wency
2012-08-20 9:35 ` [RFC V7 PATCH 01/19] memory-hotplug: rename remove_memory() to offline_memory()/offline_pages() wency
2012-08-20 9:35 ` [RFC V7 PATCH 02/19] memory-hotplug: implement offline_memory() wency
2012-08-20 9:35 ` [RFC V7 PATCH 03/19] memory-hotplug: store the node id in acpi_memory_device wency
2012-08-20 9:35 ` [RFC V7 PATCH 04/19] memory-hotplug: offline and remove memory when removing the memory device wency
2012-08-20 9:35 ` [RFC V7 PATCH 05/19] memory-hotplug: check whether memory is present or not wency
2012-08-20 9:35 ` [RFC V7 PATCH 06/19] memory-hotplug: export the function acpi_bus_remove() wency
2012-08-20 9:35 ` wency [this message]
2012-08-20 9:35 ` [RFC V7 PATCH 08/19] memory-hotplug: remove /sys/firmware/memmap/X sysfs wency
2012-08-20 9:35 ` [RFC V7 PATCH 09/19] memory-hotplug: does not release memory region in PAGES_PER_SECTION chunks wency
2012-08-20 9:35 ` [RFC V7 PATCH 10/19] memory-hotplug: add memory_block_release wency
2012-08-20 9:35 ` [RFC V7 PATCH 11/19] memory-hotplug: remove_memory calls __remove_pages wency
2012-08-20 9:35 ` [RFC V7 PATCH 12/19] memory-hotplug: introduce new function arch_remove_memory() wency
2012-08-20 9:35 ` [RFC V7 PATCH 13/19] memory-hotplug: check page type in get_page_bootmem wency
2012-08-20 9:35 ` [RFC V7 PATCH 14/19] memory-hotplug: move register_page_bootmem_info_node and put_page_bootmem for sparse-vmemmap wency
2012-08-20 9:35 ` [RFC V7 PATCH 15/19] memory-hotplug: implement register_page_bootmem_info_section of sparse-vmemmap wency
2012-08-20 9:35 ` [RFC V7 PATCH 16/19] memory-hotplug: free memmap " wency
2012-08-20 9:35 ` [RFC V7 PATCH 17/19] memory_hotplug: clear zone when the memory is removed wency
2012-08-20 9:35 ` [RFC V7 PATCH 18/19] memory-hotplug: add node_device_release wency
2012-08-20 14:09 ` Jianguo Wu
2012-08-20 9:35 ` [RFC V7 PATCH 19/19] memory-hotplug: remove sysfs file of node wency
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=1345455342-27752-8-git-send-email-wency@cn.fujitsu.com \
--to=wency@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=cl@linux.com \
--cc=cmetcalf@tilera.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=liuj97@gmail.com \
--cc=minchan.kim@gmail.com \
--cc=paulus@samba.org \
--cc=rientjes@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).