From: Chen Gong <gong.chen@linux.intel.com>
To: "canquan.shen" <shencanquan@huawei.com>
Cc: len.brown@intel.com, Bjorn Helgaas <bhelgaas@google.com>,
"shemminger@vyatta.com" <shemminger@vyatta.com>,
"yakui.zhao@intel.com" <yakui.zhao@intel.com>,
"xiaowei.yang@huawei.com" <xiaowei.yang@huawei.com>,
hanweidong <hanweidong@huawei.com>,
linqiangmin@huawei.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
khalid.aziz@hp.com
Subject: Re: [PATCH v5] acpi: Fix CPU hot removal problem
Date: Thu, 29 Sep 2011 11:14:06 +0800 [thread overview]
Message-ID: <4E83E27E.5090608@linux.intel.com> (raw)
In-Reply-To: <4E7D7468.4040506@huawei.com>
于 2011/9/24 14:10, canquan.shen 写道:
> We run linux as a guest in Xen environment. When we used the xen tools
> (xm vcpu-set <n>) to hot add and remove vcpu to and from the guest, we
> encountered the failure on vcpu removal. We found the reason is that it
> did't go to really remove cpu in the cpu removal code path.
>
> This patch adds acpi_bus_hot_remove_device in acpi_process_hotplug_notify to
> fix this issue. With this patch, it works fine for us.
>
> Signed-off-by: Canquan Shen <shencanquan@huawei.com>
> ---
> drivers/acpi/processor_driver.c | 13 +------------
> drivers/acpi/scan.c | 4 ++--
> include/acpi/acpi_bus.h | 1 +
> 3 files changed, 4 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/acpi/processor_driver.c b/drivers/acpi/processor_driver.c
> index a4e0f1b..8429688 100644
> --- a/drivers/acpi/processor_driver.c
> +++ b/drivers/acpi/processor_driver.c
> @@ -665,18 +665,7 @@ static void acpi_processor_hotplug_notify(acpi_handle handle,
> case ACPI_NOTIFY_EJECT_REQUEST:
> ACPI_DEBUG_PRINT((ACPI_DB_INFO,
> "received ACPI_NOTIFY_EJECT_REQUEST\n"));
> -
> - if (acpi_bus_get_device(handle, &device)) {
> - printk(KERN_ERR PREFIX
> - "Device don't exist, dropping EJECT\n");
> - break;
> - }
> - pr = acpi_driver_data(device);
> - if (!pr) {
> - printk(KERN_ERR PREFIX
> - "Driver data is NULL, dropping EJECT\n");
> - return;
> - }
> + acpi_bus_hot_remove_device(handle);
As the description in __acpi_os_execute(in acpi_os_hotplug_execute),
/*
* We can't run hotplug code in keventd_wq/kacpid_wq/kacpid_notify_wq
* because the hotplug code may call driver .remove() functions,
* which invoke flush_scheduled_work/acpi_os_wait_events_complete
* to flush these workqueues.
*/
If so, why not using following call:
acpi_os_hotplug_execute(acpi_bus_hot_remove_device, acpi_device->handle);
next prev parent reply other threads:[~2011-09-29 3:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-24 6:10 [PATCH v5] acpi: Fix CPU hot removal problem canquan.shen
2011-09-29 3:14 ` Chen Gong [this message]
2011-09-29 3:41 ` canquan.shen
2011-09-30 5:20 ` Bjorn Helgaas
2011-10-18 12:34 ` canquan.shen
2011-10-19 3:01 ` Chen Gong
2011-10-19 3:12 ` canquan.shen
2011-10-19 3:33 ` Bjorn Helgaas
-- strict thread matches above, loose matches on Subject: below --
2011-11-07 9:01 canquan.shen
2011-11-07 17:37 ` Len Brown
2011-11-08 0:22 ` canquan.shen
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=4E83E27E.5090608@linux.intel.com \
--to=gong.chen@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=hanweidong@huawei.com \
--cc=khalid.aziz@hp.com \
--cc=len.brown@intel.com \
--cc=linqiangmin@huawei.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shemminger@vyatta.com \
--cc=shencanquan@huawei.com \
--cc=xiaowei.yang@huawei.com \
--cc=yakui.zhao@intel.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