public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Toshi Kani <toshi.kani@hp.com>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI/hotplug: Fix STARTING/DYING action in acpi_cpu_soft_notify()
Date: Tue, 20 May 2014 00:55:51 +0200	[thread overview]
Message-ID: <2011129.WMiXDPUasW@vostro.rjw.lan> (raw)
In-Reply-To: <1399557539-7282-1-git-send-email-toshi.kani@hp.com>

On Thursday, May 08, 2014 07:58:59 AM Toshi Kani wrote:
> During CPU online/offline testing on a large system, one of the
> processors got stuck after the message "bad: scheduling from the
> idle thread!".  The problem is that acpi_cpu_soft_notify() calls
> acpi_bus_get_device() for all action types.  CPU_STARTING and
> CPU_DYING do not allow the notify handlers to sleep.  However,
> acpi_bus_get_device() can sleep in acpi_ut_acquire_mutex().
> 
> Change acpi_cpu_soft_notify() to return immediately for CPU_STARTING
> and CPU_DYING as they have no action in this handler.
> 
> Signed-off-by: Toshi Kani <toshi.kani@hp.com>

Queued up for 3.16, thanks!

> ---
>  drivers/acpi/processor_driver.c |    7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/drivers/acpi/processor_driver.c b/drivers/acpi/processor_driver.c
> index 7f70f31..4fcbd67 100644
> --- a/drivers/acpi/processor_driver.c
> +++ b/drivers/acpi/processor_driver.c
> @@ -121,6 +121,13 @@ static int acpi_cpu_soft_notify(struct notifier_block *nfb,
>  	struct acpi_processor *pr = per_cpu(processors, cpu);
>  	struct acpi_device *device;
>  
> +	/*
> +	 * CPU_STARTING and CPU_DYING must not sleep. Return here since
> +	 * acpi_bus_get_device() may sleep.
> +	 */
> +	if (action == CPU_STARTING || action == CPU_DYING)
> +		return NOTIFY_DONE;
> +
>  	if (!pr || acpi_bus_get_device(pr->handle, &device))
>  		return NOTIFY_DONE;
>  
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

  reply	other threads:[~2014-05-19 22:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-08 13:58 [PATCH] ACPI/hotplug: Fix STARTING/DYING action in acpi_cpu_soft_notify() Toshi Kani
2014-05-19 22:55 ` Rafael J. Wysocki [this message]
2014-05-19 22:57   ` Toshi Kani

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=2011129.WMiXDPUasW@vostro.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=toshi.kani@hp.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