public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Deepthi Dharwar <deepthi@linux.vnet.ibm.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Nicolas Kalkhof <nkalkhof@web.de>,
	linux-kernel@vger.kernel.org,
	Linux PM mailing list <linux-pm@vger.kernel.org>
Subject: Re: Too many poll_idle cpu calls in kernel 3.2 rc-series
Date: Tue, 29 Nov 2011 16:37:01 +0530	[thread overview]
Message-ID: <4ED4BCD5.3090308@linux.vnet.ibm.com> (raw)
In-Reply-To: <20111128204412.GM24062@one.firstfloor.org>

On 11/29/2011 02:14 AM, Andi Kleen wrote:

> On Mon, Nov 28, 2011 at 09:31:13PM +0100, Nicolas Kalkhof wrote:
>> Andi,
>>
>> correct. The issue was introduced somewhere between 3.1 final and 3.2-rc1. I've tried to track down the bad commit but so far I haven't been successfull. The only workaround I found is to set the idle boot parameter to mwait and to disable CONFIG_INTEL_IDLE. Somehow the kernel seems to set idle to poll by default - no idea why :-(. I wonder if other mobile sandy bridge cpus are affected as well.
> 
> There are only a few changesets affecting drivers/idle
> 
> Can you try to git revert 
> 
> 46bcfad7a819bd17ac4e831b04405152d59784ab
> 4202735e8ab6ecfb0381631a0d0b58fefe0bd4e2
> e978aa7d7d57d04eb5f88a7507c4fb98577def77
> 
> ?
> 
> -Andi


Hi,

I am guessing that for workaround just setting the idle boot parameter
to mwait should work. Have u tested this without disabling
CONFIG_INTEL_IDLE ?

Also one thing to note from your logs is, cpu is not entering any of the
other C states except for POLL. Can you also check if your are enabling
only POLL for idle. I am able to enter deeper C-states on i5-2540M with
Intel_Idle enabled.

Power top o/p:
-------------

            Core    |             CPU 0               CPU 1
POLL        0.0%    | POLL        0.0%    0.0 ms      0.0%    0.0 ms
C1-SNB      1.4%    | C1-SNB      2.2%    0.7 ms      0.5%    0.9 ms
C3-SNB      0.9%    | C3-SNB      1.6%    1.2 ms      0.1%    1.2 ms
C6-SNB      0.2%    | C6-SNB      0.3%    1.6 ms      0.0%    0.9 ms
C7-SNB     95.8%    | C7-SNB     93.7%    3.7 ms     97.8%   15.1 ms


Regards,
Deepthi


  reply	other threads:[~2011-11-29 11:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-28 20:31 Too many poll_idle cpu calls in kernel 3.2 rc-series Nicolas Kalkhof
2011-11-28 20:44 ` Andi Kleen
2011-11-29 11:07   ` Deepthi Dharwar [this message]
2011-12-10  7:33     ` Mike Galbraith
  -- strict thread matches above, loose matches on Subject: below --
2011-11-30 11:54 Nicolas Kalkhof
2011-11-27 20:13 Nicolas Kalkhof
2011-11-28 19:33 ` Andi Kleen
2011-11-28 20:01 ` Srivatsa S. Bhat
2011-11-29 10:37   ` Deepthi Dharwar

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=4ED4BCD5.3090308@linux.vnet.ibm.com \
    --to=deepthi@linux.vnet.ibm.com \
    --cc=andi@firstfloor.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox