From: Venki Pallipadi <venkatesh.pallipadi@intel.com>
To: David Brownell <david-b@pacbell.net>
Cc: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-acpi@vger.kernel.org, Len Brown <lenb@kernel.org>
Subject: Re: 2.6.25 regression: powertop says 120K wakeups/sec
Date: Fri, 28 Mar 2008 15:56:04 -0700 [thread overview]
Message-ID: <20080328225604.GA7136@linux-os.sc.intel.com> (raw)
In-Reply-To: <200803281509.23107.david-b@pacbell.net>
On Fri, Mar 28, 2008 at 03:09:22PM -0700, David Brownell wrote:
> On Friday 28 March 2008, Pallipadi, Venkatesh wrote:
> > You should have a dmesg line which looks like
> > ACPI: CPU0 (power states: C1[C1] C2[C2]
> > Do you see C2 in such line?
>
> Yes:
>
> ACPI: CPU0 (power states: C1[C1] C2[C2])
David,
I think I figured out the bug...
Can you try the below patch and confirm that it works (over upstream - ignore
the earlier revert patch I sent to you).
Thanks,
Venki
----
Patch to fix huge number of wakeups reported due to recent changes in
processor_idle.c. The problem was that the entry_method determination was
broken due to one of the recent commits (bc71bec91f987) causing
C1 entry to not to go to halt. This should also fix the hang reported here.
http://bugzilla.kernel.org/show_bug.cgi?id=10093
Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
---
drivers/acpi/processor_idle.c | 4 ++++
1 file changed, 4 insertions(+)
Index: linux-2.6/drivers/acpi/processor_idle.c
===================================================================
--- linux-2.6.orig/drivers/acpi/processor_idle.c 2008-03-28 15:31:13.000000000 -0700
+++ linux-2.6/drivers/acpi/processor_idle.c 2008-03-28 15:40:50.000000000 -0700
@@ -848,6 +848,7 @@ static int acpi_processor_get_power_info
/* all processors need to support C1 */
pr->power.states[ACPI_STATE_C1].type = ACPI_STATE_C1;
pr->power.states[ACPI_STATE_C1].valid = 1;
+ pr->power.states[ACPI_STATE_C1].entry_method = ACPI_CSTATE_HALT;
}
/* the C0 state only exists as a filler in our array */
pr->power.states[ACPI_STATE_C0].valid = 1;
@@ -960,6 +961,9 @@ static int acpi_processor_get_power_info
cx.address);
}
+ if (cx.type == ACPI_STATE_C1) {
+ cx.valid = 1;
+ }
obj = &(element->package.elements[2]);
if (obj->type != ACPI_TYPE_INTEGER)
next prev parent reply other threads:[~2008-03-28 22:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-22 20:24 2.6.25 regression: powertop says 120K wakeups/sec David Brownell
2008-03-23 0:35 ` Andrew Morton
2008-03-23 18:04 ` Alexey Starikovskiy
2008-03-28 19:01 ` David Brownell
2008-03-28 19:13 ` Pallipadi, Venkatesh
2008-03-28 19:44 ` David Brownell
2008-03-28 20:30 ` Venki Pallipadi
2008-03-28 21:09 ` David Brownell
2008-03-28 21:55 ` Pallipadi, Venkatesh
2008-03-28 22:09 ` David Brownell
2008-03-28 22:56 ` Venki Pallipadi [this message]
2008-03-28 23:01 ` Rafael J. Wysocki
2008-03-28 23:07 ` Pallipadi, Venkatesh
2008-03-31 17:42 ` Mark Lord
2008-03-31 18:34 ` Pallipadi, Venkatesh
2008-03-28 23:36 ` David Brownell
2008-03-28 23:51 ` Pallipadi, Venkatesh
2008-03-29 0:15 ` David Brownell
-- strict thread matches above, loose matches on Subject: below --
2008-04-24 8:51 Daniel Klaffenbach
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=20080328225604.GA7136@linux-os.sc.intel.com \
--to=venkatesh.pallipadi@intel.com \
--cc=akpm@linux-foundation.org \
--cc=david-b@pacbell.net \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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