From: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
To: Wen Congyang <wency@cn.fujitsu.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-acpi@vger.kernel.org, Len Brown <len.brown@intel.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Andrew Morton <akpm@linux-foundation.org>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
Jiang Liu <jiang.liu@huawei.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Minchan Kim <minchan.kim@gmail.com>, Mel Gorman <mgorman@suse.de>,
David Rientjes <rientjes@google.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Toshi Kani <toshi.kani@hp.com>, Jiang Liu <liuj97@gmail.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Christoph Lameter <cl@linux.com>
Subject: Re: [Patch v5 2/7] acpi,memory-hotplug: deal with eject request in hotplug queue
Date: Thu, 15 Nov 2012 18:13:11 +0900 [thread overview]
Message-ID: <50A4B227.4050307@jp.fujitsu.com> (raw)
In-Reply-To: <1352962777-24407-3-git-send-email-wency@cn.fujitsu.com>
2012/11/15 15:59, Wen Congyang wrote:
> 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
>
> We handle the 1st case in the module acpi_memhotplug, and handle
> the 2nd case in ACPI eject notification. This 2 events may happen
> at the same time, so we may touch acpi_memory_device.res_list at
> the same time. This patch reimplements memory-hotremove support
> through an ACPI eject notification. Now the memory device is
> offlined and hotremoved only in the function acpi_memory_device_remove()
> which is protected by device_lock().
>
> 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>
> CC: Rafael J. Wysocki <rjw@sisk.pl>
> CC: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> Signed-off-by: Wen Congyang <wency@cn.fujitsu.com>
> ---
Reviewed-by: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
Thanks,
Yasuaki Ishimatsu
> drivers/acpi/acpi_memhotplug.c | 87 +++++-------------------------------------
> 1 file changed, 9 insertions(+), 78 deletions(-)
>
> diff --git a/drivers/acpi/acpi_memhotplug.c b/drivers/acpi/acpi_memhotplug.c
> index 2918be1..6e12042 100644
> --- a/drivers/acpi/acpi_memhotplug.c
> +++ b/drivers/acpi/acpi_memhotplug.c
> @@ -272,40 +272,6 @@ static int acpi_memory_enable_device(struct acpi_memory_device *mem_device)
> return 0;
> }
>
> -static int acpi_memory_powerdown_device(struct acpi_memory_device *mem_device)
> -{
> - acpi_status status;
> - struct acpi_object_list arg_list;
> - union acpi_object arg;
> - unsigned long long current_status;
> -
> -
> - /* Issue the _EJ0 command */
> - arg_list.count = 1;
> - arg_list.pointer = &arg;
> - arg.type = ACPI_TYPE_INTEGER;
> - arg.integer.value = 1;
> - status = acpi_evaluate_object(mem_device->device->handle,
> - "_EJ0", &arg_list, NULL);
> - /* Return on _EJ0 failure */
> - if (ACPI_FAILURE(status)) {
> - ACPI_EXCEPTION((AE_INFO, status, "_EJ0 failed"));
> - return -ENODEV;
> - }
> -
> - /* Evalute _STA to check if the device is disabled */
> - status = acpi_evaluate_integer(mem_device->device->handle, "_STA",
> - NULL, ¤t_status);
> - if (ACPI_FAILURE(status))
> - return -ENODEV;
> -
> - /* Check for device status. Device should be disabled */
> - if (current_status & ACPI_STA_DEVICE_ENABLED)
> - return -EINVAL;
> -
> - return 0;
> -}
> -
> static int acpi_memory_remove_memory(struct acpi_memory_device *mem_device)
> {
> int result;
> @@ -325,34 +291,11 @@ static int acpi_memory_remove_memory(struct acpi_memory_device *mem_device)
> return 0;
> }
>
> -static int acpi_memory_disable_device(struct acpi_memory_device *mem_device)
> -{
> - int result;
> -
> - /*
> - * Ask the VM to offline this memory range.
> - * Note: Assume that this function returns zero on success
> - */
> - result = acpi_memory_remove_memory(mem_device);
> - if (result)
> - return result;
> -
> - /* Power-off and eject the device */
> - result = acpi_memory_powerdown_device(mem_device);
> - if (result) {
> - /* Set the status of the device to invalid */
> - mem_device->state = MEMORY_INVALID_STATE;
> - return result;
> - }
> -
> - mem_device->state = MEMORY_POWER_OFF_STATE;
> - return result;
> -}
> -
> static void acpi_memory_device_notify(acpi_handle handle, u32 event, void *data)
> {
> struct acpi_memory_device *mem_device;
> struct acpi_device *device;
> + struct acpi_eject_event *ej_event = NULL;
> u32 ost_code = ACPI_OST_SC_NON_SPECIFIC_FAILURE; /* default */
>
> switch (event) {
> @@ -394,31 +337,19 @@ static void acpi_memory_device_notify(acpi_handle handle, u32 event, void *data)
> break;
> }
>
> - /*
> - * Currently disabling memory device from kernel mode
> - * TBD: Can also be disabled from user mode scripts
> - * TBD: Can also be disabled by Callback registration
> - * with generic sysfs driver
> - */
> - if (acpi_memory_disable_device(mem_device)) {
> - printk(KERN_ERR PREFIX "Disable memory device\n");
> - /*
> - * If _EJ0 was called but failed, _OST is not
> - * necessary.
> - */
> - if (mem_device->state == MEMORY_INVALID_STATE)
> - return;
> -
> + ej_event = kmalloc(sizeof(*ej_event), GFP_KERNEL);
> + if (!ej_event) {
> + pr_err(PREFIX "No memory, dropping EJECT\n");
> break;
> }
>
> - /*
> - * TBD: Invoke acpi_bus_remove to cleanup data structures
> - */
> + ej_event->handle = handle;
> + ej_event->event = ACPI_NOTIFY_EJECT_REQUEST;
> + acpi_os_hotplug_execute(acpi_bus_hot_remove_device,
> + (void *)ej_event);
>
> - /* _EJ0 succeeded; _OST is not necessary */
> + /* eject is performed asynchronously */
> return;
> -
> default:
> ACPI_DEBUG_PRINT((ACPI_DB_INFO,
> "Unsupported event [0x%x]\n", event));
>
--
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>
next prev parent reply other threads:[~2012-11-15 9:14 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 6:59 [Patch v5 0/7] acpi,memory-hotplug: implement framework for hot removing memory Wen Congyang
2012-11-15 6:59 ` [Patch v5 1/7] acpi,memory-hotplug : add memory offline code to acpi_memory_device_remove() Wen Congyang
2012-11-15 23:03 ` David Rientjes
2012-11-15 6:59 ` [Patch v5 2/7] acpi,memory-hotplug: deal with eject request in hotplug queue Wen Congyang
2012-11-15 9:13 ` Yasuaki Ishimatsu [this message]
2012-11-15 22:09 ` Toshi Kani
2012-11-15 23:32 ` David Rientjes
2012-11-16 1:54 ` Wen Congyang
2012-11-15 6:59 ` [Patch v5 3/7] acpi_memhotplug.c: fix memory leak when memory device is unbound from the module acpi_memhotplug Wen Congyang
2012-11-15 9:15 ` Yasuaki Ishimatsu
2012-11-15 23:34 ` David Rientjes
2012-11-15 6:59 ` [Patch v5 4/7] acpi_memhotplug.c: free memory device if acpi_memory_enable_device() failed Wen Congyang
2012-11-15 9:17 ` Yasuaki Ishimatsu
2012-11-15 23:36 ` David Rientjes
2012-11-15 6:59 ` [Patch v5 5/7] acpi_memhotplug.c: don't allow to eject the memory device if it is being used Wen Congyang
2012-11-15 9:20 ` Yasuaki Ishimatsu
2012-11-15 23:39 ` David Rientjes
2012-11-29 13:15 ` andywu106建国
2012-11-15 6:59 ` [Patch v5 6/7] acpi_memhotplug.c: bind the memory device when the driver is being loaded Wen Congyang
2012-11-15 9:22 ` Yasuaki Ishimatsu
2012-11-15 23:40 ` David Rientjes
2012-11-15 6:59 ` [Patch v5 7/7] acpi_memhotplug.c: auto bind the memory device which is hotplugged before the driver is loaded Wen Congyang
2012-11-15 9:57 ` Yasuaki Ishimatsu
2012-11-15 22:45 ` Toshi Kani
2012-11-15 22:51 ` [Patch v5 0/7] acpi,memory-hotplug: implement framework for hot removing memory David Rientjes
2012-11-15 23:22 ` Rafael J. Wysocki
2012-11-15 23:33 ` Rafael J. Wysocki
2012-11-16 0:28 ` Rafael J. Wysocki
2012-11-16 0:40 ` Rafael J. Wysocki
2012-11-16 0:40 ` Toshi Kani
2012-11-16 1:02 ` Rafael J. Wysocki
2012-11-16 1:07 ` Yasuaki Ishimatsu
2012-11-16 1:28 ` Rafael J. Wysocki
2012-11-16 1:31 ` Yasuaki Ishimatsu
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=50A4B227.4050307@jp.fujitsu.com \
--to=isimatu.yasuaki@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=cl@linux.com \
--cc=jiang.liu@huawei.com \
--cc=konrad.wilk@oracle.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=laijs@cn.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=mgorman@suse.de \
--cc=minchan.kim@gmail.com \
--cc=paulus@samba.org \
--cc=rientjes@google.com \
--cc=rjw@sisk.pl \
--cc=toshi.kani@hp.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox