From: Shaohua Li <shaohua.li@intel.com>
To: linux acpi <linux-acpi@vger.kernel.org>
Cc: Len Brown <lenb@kernel.org>, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [patch 1/2]intel_idle: fix misuse API - resend
Date: Mon, 13 Jun 2011 10:51:43 +0800 [thread overview]
Message-ID: <1307933503.15392.104.camel@sli10-conroe> (raw)
In-Reply-To: <1307068954.15392.52.camel@sli10-conroe>
On Fri, 2011-06-03 at 10:42 +0800, Shaohua Li wrote:
> smp_call_function() only lets all other CPUs execute specific
> function, while we expect all CPUs do in intel_idle. Without
> the fix, we could have one cpu has auto_demotion enabled or
> has no boradcast timer setup. Usually we don't see impact
> because auto demotion just harms power and the intel_idle init
> is called in CPU 0, where boradcast timer delivers interrupt,
> but this still could be a problem.
has any comments on these? NACK or merge?
prev parent reply other threads:[~2011-06-13 2:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 2:42 [patch 1/2]intel_idle: fix misuse API - resend Shaohua Li
2011-06-13 2:51 ` Shaohua Li [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=1307933503.15392.104.camel@sli10-conroe \
--to=shaohua.li@intel.com \
--cc=akpm@linux-foundation.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
/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