public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Andreas Hartmann <andihartmann@freenet.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: intel_ips produces constant load of 1
Date: Fri, 25 Mar 2011 11:24:43 -0700	[thread overview]
Message-ID: <20110325112443.7caf4429@jbarnes-desktop> (raw)
In-Reply-To: <4D8CDD93.3030203@dualc.maya.org>

On Fri, 25 Mar 2011 19:23:15 +0100
Andreas Hartmann <andihartmann@freenet.de> wrote:

> Jesse Barnes wrote:
> > On Mon, 21 Mar 2011 11:04:04 -0700
> > Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> > 
> >>> ps aux | grep ips
> >>> root       593  0.0  0.0      0     0 ?        S    17:20   0:00
> >>> [ips-adjust]
> >>> root       594  0.0  0.0      0     0 ?        D    17:20   0:00
> >>> [ips-monitor]
> >>>
> >>> If the module isn't loaded, the load of the machine in idle mode is 0 as
> >>> expected.  
> >>
> >> This is a reporting problem, and probably due to the schedule() call
> >> and associated task state in the ips-monitor thread.  I thought setting
> >> the task state to interruptible would prevent this, but it seems like
> >> it's not enough for the deferrable on-stack timers?
> >>
> >> At any rate, it's not actually causing increased CPU usage, so you can
> >> safely ignore it until we have a fix.
> > 
> > Oops, one task uses interruptible correctly, but the monitor thread
> > doesn't.
> > 
> > Does this patch fix your load average?
> 
> The patch works fine:
> 
> ps aux | grep ips
> root     22427  0.0  0.0      0     0 ?        S    19:15   0:00
> [ips-adjust]
> root     22428  0.0  0.0      0     0 ?        S    19:15   0:00
> [ips-monitor]

Great, thanks for testing.  I'll get the fix over to Matthew.

> btw: what does this mean (first line):
> 
> 
> kernel: [ 6610.030205] intel ips 0000:00:1f.6: CPU TDP doesn't match
> expected value (found 25, expected 29)

Each SKU has a default TDP.  In your case that's 29W.  But the BIOS can
override that value with a lower one if the platform (chassis, board,
fans, etc) isn't designed to dissipate the full amount.


-- 
Jesse Barnes, Intel Open Source Technology Center

      reply	other threads:[~2011-03-25 18:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-19 15:38 intel_ips produces constant load of 1 Andreas Hartmann
2011-03-21 18:04 ` Jesse Barnes
2011-03-22  7:00   ` Andreas Hartmann
2011-03-22 15:49     ` Jesse Barnes
2011-03-22 20:25   ` Jesse Barnes
2011-03-23 18:15     ` Andreas Hartmann
2011-03-23 18:20       ` Jesse Barnes
2011-03-23 19:44         ` Andreas Hartmann
2011-03-25 18:23     ` Andreas Hartmann
2011-03-25 18:24       ` Jesse Barnes [this message]

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=20110325112443.7caf4429@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --cc=andihartmann@freenet.de \
    --cc=linux-kernel@vger.kernel.org \
    /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