From: Jan Willies <jan@willies.info>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-acpi@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Venki Pallipadi <venkatesh.pallipadi@intel.com>
Subject: Re: 100% C0 with 2.6.25-rc
Date: Fri, 22 Feb 2008 16:56:22 +0100 [thread overview]
Message-ID: <47BEF0A6.9000405@willies.info> (raw)
In-Reply-To: <200802211733.54759.rjw@sisk.pl>
Rafael J. Wysocki wrote:
> On Thursday, 21 of February 2008, Jan Willies wrote:
>> Since 2.6.25-rc1 I have a lot of wakeups/s (≈134191,4) and spend 100% in C0.
>> It worked fine with 2.6.24 and commandline nolapic. Without nolapic I had 80k
>> wakeups/s after some time, but not right from the start like now.
>
> We have a regression from 2.6.24, apparently interrupts-related.
After a lot of bisecting I've found the bad commit:
9b12e18cdc1553de62d931e73443c806347cd974 is first bad commit
commit 9b12e18cdc1553de62d931e73443c806347cd974
Author: venkatesh.pallipadi@intel.com <venkatesh.pallipadi@intel.com>
Date: Thu Jan 31 17:35:05 2008 -0800
ACPI: cpuidle: Support C1 idle time accounting
Show C1 idle time in /sysfs cpuidle interface. C1 idle time may not
be entirely accurate in all cases. It includes the time spent
in the interrupt handler after wakeup with "hlt" based C1. But, it will
be accurate with "mwait" based C1.
Reverting the commit brings my laptop back to C2.
HTH
- Jan
next prev parent reply other threads:[~2008-02-22 16:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <47BD600F.9090502@willies.info>
2008-02-21 16:33 ` 100% C0 with 2.6.25-rc Rafael J. Wysocki
2008-02-22 15:56 ` Jan Willies [this message]
2008-02-22 17:03 ` Pallipadi, Venkatesh
2008-02-22 17:33 ` Pallipadi, Venkatesh
2008-02-22 17:50 ` Jan Willies
2008-02-22 17:55 ` Pallipadi, Venkatesh
2008-02-22 18:16 ` Jan Willies
[not found] ` <B5B0CFF685D7DF46A05CF1678CFB42ED20E00658@orsmsx423.amr.corp.intel.com>
2008-02-29 18:24 ` Venki Pallipadi
2008-03-26 4:58 ` Len Brown
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=47BEF0A6.9000405@willies.info \
--to=jan@willies.info \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=tglx@linutronix.de \
--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