Re: [PATCH 1/2] Use kacpi_hotplug_wq to handle container hotplug event.

2012-10-24 Thread Tang Chen
On 10/25/2012 01:33 AM, Toshi Kani wrote: On Tue, 2012-10-23 at 21:10 +0800, Tang Chen wrote: As the comments in __acpi_os_execute() said: We can't run hotplug code in keventd_wq/kacpid_wq/kacpid_notify_wq because the hotplug code may call driver .remove() functions,

Re: [PATCH 1/2] Use kacpi_hotplug_wq to handle container hotplug event.

2012-10-24 Thread Toshi Kani
On Tue, 2012-10-23 at 21:10 +0800, Tang Chen wrote: > As the comments in __acpi_os_execute() said: > > 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

Re: [PATCH 1/2] Use kacpi_hotplug_wq to handle container hotplug event.

2012-10-24 Thread Toshi Kani
On Tue, 2012-10-23 at 21:10 +0800, Tang Chen wrote: As the comments in __acpi_os_execute() said: 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

Re: [PATCH 1/2] Use kacpi_hotplug_wq to handle container hotplug event.

2012-10-24 Thread Tang Chen
On 10/25/2012 01:33 AM, Toshi Kani wrote: On Tue, 2012-10-23 at 21:10 +0800, Tang Chen wrote: As the comments in __acpi_os_execute() said: We can't run hotplug code in keventd_wq/kacpid_wq/kacpid_notify_wq because the hotplug code may call driver .remove() functions,

Re: [PATCH 1/2] Use kacpi_hotplug_wq to handle container hotplug event.

2012-10-23 Thread Yinghai Lu
On Tue, Oct 23, 2012 at 6:10 AM, Tang Chen wrote: > As the comments in __acpi_os_execute() said: > > 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

[PATCH 1/2] Use kacpi_hotplug_wq to handle container hotplug event.

2012-10-23 Thread Tang Chen
As the comments in __acpi_os_execute() said: 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.

[PATCH 1/2] Use kacpi_hotplug_wq to handle container hotplug event.

2012-10-23 Thread Tang Chen
As the comments in __acpi_os_execute() said: 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.

Re: [PATCH 1/2] Use kacpi_hotplug_wq to handle container hotplug event.

2012-10-23 Thread Yinghai Lu
On Tue, Oct 23, 2012 at 6:10 AM, Tang Chen tangc...@cn.fujitsu.com wrote: As the comments in __acpi_os_execute() said: 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