From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: Nicolas Kalkhof <nkalkhof@web.de>
Cc: linux-kernel@vger.kernel.org,
Linux PM mailing list <linux-pm@vger.kernel.org>,
Deepthi Dharwar <deepthi@linux.vnet.ibm.com>
Subject: Re: Too many poll_idle cpu calls in kernel 3.2 rc-series
Date: Tue, 29 Nov 2011 01:31:49 +0530 [thread overview]
Message-ID: <4ED3E8AD.6050304@linux.vnet.ibm.com> (raw)
In-Reply-To: <1587582695.5658131.1322424808507.JavaMail.fmail@mwmweb005>
Adding linux-pm mailing list to CC.
Thanks,
Srivatsa S. Bhat
On 11/28/2011 01:43 AM, Nicolas Kalkhof wrote:
> the kernel v3.2 series shows excessive poll_idle calls during system idle phases causing the cpu
> (mobile i7 2620M) to heat up and draw additional 10% more power. All kernel versions between
> 3.2-rc1 and 3.2-rc3 are affected. Perf Top and Powertop both show the same issue.
> I've posted a similar bug report before: http://marc.info/?l=linux-kernel&m=132164909313594&w=2
> and used perf top -U to verify the poll_idle calls as requested.
>
> dmesg and kernel .config attached.
>
> Could someone please confirm this issue?
>
> Thanks and Regards
> Nic
>
> perf top -U shows:
> Events: 30K cycles
> 97.88% [kernel] [k] poll_idle
> 0.17% [kernel] [k] sdhci_irq
> 0.08% [kernel] [k] unix_poll
> 0.06% [kernel] [k] _raw_spin_lock_irqsave
> 0.06% [kernel] [k] page_fault
> 0.05% [kernel] [k] fget_light
> 0.05% [kernel] [k] format_decode
> 0.04% [kernel] [k] kmem_cache_alloc
> 0.04% [kernel] [k] clear_page
> 0.04% [kernel] [k] _raw_spin_unlock_irqrestore
> 0.03% [kernel] [k] do_select
> 0.03% [kernel] [k] seq_printf
> 0.03% [kernel] [k] vfs_read
> 0.03% [kernel] [k] _raw_spin_lock
> 0.03% [kernel] [k] vsnprintf
> 0.03% [kernel] [k] number.clone.1
> 0.03% [kernel] [k] fput
>
> Powertop shows:
> n Avg residency P-states (frequencies)
> C0 (cpu running) ( 5.4%) Turbo Mode 1.5%
> polling 1.8ms (94.6%) 2.71 Ghz 0.1%
> C1 mwait 0.0ms ( 0.0%) 2.21 Ghz 0.1%
> C2 mwait 0.0ms ( 0.0%) 1400 Mhz 0.1%
> C3 mwait 0.0ms ( 0.0%) 800 Mhz 98.2%
> C4 mwait 0.0ms ( 0.0%)
> Wakeups-from-idle per second : 529.4 interval: 5.0s
>
next prev parent reply other threads:[~2011-11-28 20:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-27 20:13 Too many poll_idle cpu calls in kernel 3.2 rc-series Nicolas Kalkhof
2011-11-28 19:33 ` Andi Kleen
2011-11-28 20:01 ` Srivatsa S. Bhat [this message]
2011-11-29 10:37 ` Deepthi Dharwar
-- strict thread matches above, loose matches on Subject: below --
2011-11-28 20:31 Nicolas Kalkhof
2011-11-28 20:44 ` Andi Kleen
2011-11-29 11:07 ` Deepthi Dharwar
2011-12-10 7:33 ` Mike Galbraith
2011-11-30 11:54 Nicolas Kalkhof
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=4ED3E8AD.6050304@linux.vnet.ibm.com \
--to=srivatsa.bhat@linux.vnet.ibm.com \
--cc=deepthi@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nkalkhof@web.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.