From: Daniel Klaffenbach <danielklaffenbach@gmail.com>
To: Len Brown <lenb@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
venkatesh.pallipadi@intel.com
Subject: Re: [2.6.25-stable PATCH] regression: powertop says 120K wakeups/sec
Date: Mon, 28 Apr 2008 12:09:47 +0200 [thread overview]
Message-ID: <200804281209.47927.danielklaffenbach@gmail.com> (raw)
In-Reply-To: <200804242015.19462.lenb@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 922 bytes --]
> commit 0fda6b403f0eca66ad8a7c946b3996e359100443
>
> 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.
>
> http://lkml.org/lkml/2008/3/22/124
>
> Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
> Signed-off-by: Len Brown <len.brown@intel.com>
OK, this fixes my issue with the massive amount of wakeups:
http://lkml.org/lkml/2008/4/24/70
However the CPU does not really go to C1 or C2 after applying this patch to
the latest git kernel:
Cn Avg residency P-states (frequencies)
C0 (cpu running) (99,4%) 1,80 Ghz 0,0%
C1 0,0ms ( 0,0%) 1,60 Ghz 0,0%
C2 0,0ms ( 0,6%) 800 Mhz 100,0%
- Daniel
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-04-28 10:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-25 0:15 [2.6.25-stable PATCH] regression: powertop says 120K wakeups/sec Len Brown
2008-04-26 1:51 ` [stable] " Greg KH
2008-04-28 10:09 ` Daniel Klaffenbach [this message]
2008-04-28 16:36 ` Pallipadi, Venkatesh
2008-04-28 18:01 ` Daniel Klaffenbach
2008-04-28 21:13 ` Pallipadi, Venkatesh
2008-04-28 21:39 ` Ray Lee
2008-04-29 9:14 ` 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=200804281209.47927.danielklaffenbach@gmail.com \
--to=danielklaffenbach@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@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