From: Len Brown <lenb@kernel.org>
To: akpm@linux-foundation.org
Cc: linux-acpi@vger.kernel.org, venkatesh.pallipadi@intel.com
Subject: Re: [patch 2/3] cpuidle hang fix
Date: Sun, 29 Apr 2007 00:42:40 -0400 [thread overview]
Message-ID: <200704290042.40625.lenb@kernel.org> (raw)
In-Reply-To: <200704260703.l3Q73xdQ023270@shell0.pdx.osdl.net>
Applied to acpi-test
thanks,
-Len
On Thursday 26 April 2007 03:03, akpm@linux-foundation.org wrote:
> From: Venki Pallipadi <venkatesh.pallipadi@intel.com>
>
> Prevent hang on x86-64, when ACPI processor driver is added as a module on
> a system that does not support C-states.
>
> x86-64 expects all idle handlers to enable interrupts before returning from
> idle handler. This is due to enter_idle(), exit_idle() races. Make
> cpuidle_idle_call() confirm to this when there is no pm_idle_old.
>
> Also, cpuidle look at the return values of attch_driver() and set
> current_driver to NULL if attach fails on all CPUs.
>
> Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
>
> drivers/cpuidle/cpuidle.c | 2 ++
> drivers/cpuidle/driver.c | 15 ++++++++++++---
> 2 files changed, 14 insertions(+), 3 deletions(-)
>
> diff -puN drivers/cpuidle/cpuidle.c~cpuidle-hang-fix drivers/cpuidle/cpuidle.c
> --- a/drivers/cpuidle/cpuidle.c~cpuidle-hang-fix
> +++ a/drivers/cpuidle/cpuidle.c
> @@ -43,6 +43,8 @@ static void cpuidle_idle_call(void)
> if (dev->status != CPUIDLE_STATUS_DOIDLE) {
> if (pm_idle_old)
> pm_idle_old();
> + else
> + local_irq_enable();
> return;
> }
>
> diff -puN drivers/cpuidle/driver.c~cpuidle-hang-fix drivers/cpuidle/driver.c
> --- a/drivers/cpuidle/driver.c~cpuidle-hang-fix
> +++ a/drivers/cpuidle/driver.c
> @@ -107,11 +107,20 @@ int cpuidle_switch_driver(struct cpuidle
> cpuidle_curr_driver = drv;
>
> if (drv) {
> + int ret = 1;
> list_for_each_entry(dev, &cpuidle_detected_devices, device_list)
> - cpuidle_attach_driver(dev);
> - if (cpuidle_curr_governor)
> + if (cpuidle_attach_driver(dev) == 0)
> + ret = 0;
> +
> + /* If attach on all devices fail, switch to NULL driver */
> + if (ret)
> + cpuidle_curr_driver = NULL;
> +
> + if (cpuidle_curr_driver && cpuidle_curr_governor) {
> + printk(KERN_INFO "cpuidle: using driver %s\n",
> + drv->name);
> cpuidle_install_idle_handler();
> - printk(KERN_INFO "cpuidle: using driver %s\n", drv->name);
> + }
> }
>
> return 0;
> _
> -
> 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
>
prev parent reply other threads:[~2007-04-29 4:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 7:03 [patch 2/3] cpuidle hang fix akpm
2007-04-29 4:42 ` Len Brown [this message]
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=200704290042.40625.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-acpi@vger.kernel.org \
--cc=venkatesh.pallipadi@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