public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Stephen Clark <Stephen.Clark@seclark.us>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Power Saving
Date: Mon, 19 Nov 2007 20:12:36 -0500	[thread overview]
Message-ID: <20071120011236.GA17420@redhat.com> (raw)
In-Reply-To: <474232D9.20407@seclark.us>

On Mon, Nov 19, 2007 at 08:05:29PM -0500, Stephen Clark wrote:
 
 > >I think by throttling, you actually mean changing frequency/voltage ?
 > >(throttling is something else, where the CPU skips every n cycles,
 > > which doesn't actually save any power)
 > >
 > well what about the info from /proc/
 > 
 > cat /proc/acpi/processor/CPU0/info
 > processor id:            0
 > acpi id:                 0
 > bus mastering control:   no
 > power management:        yes
 > throttling control:      yes
 > limit interface:         yes
 > 
 > and:
 > cat /proc/acpi/processor/CPU0/throttling
 > state count:             2
 > active state:            T0
 > states:
 >    *T0:                  00%
 >     T1:                  50%

See above. These are throttling states, used typically
if the system is overheating.

 > [root@joker ~]# cat /proc/acpi/processor/CPU0/power
 > active state:            C2
 > max_cstate:              C8
 > bus master activity:     d18324c9
 > states:
 >     C1:                  type[C1] promotion[C2] demotion[--] 
 > latency[000] usage[01340140]
 >    *C2:                  type[C2] promotion[--] demotion[C1] 
 > latency[090] usage[02980043]
 > 
 > ????

C states are unrelated to frequency/voltage scaling (which are P states)
They get taken advantage of automatically by ACPI as you can
see from the usage fields.

	Dave

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2007-11-20  1:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-20  0:41 Power Saving Stephen Clark
2007-11-20  0:54 ` Dave Jones
2007-11-20  1:05   ` Stephen Clark
2007-11-20  1:12     ` Dave Jones [this message]
2007-11-20  1:21       ` H. Peter Anvin
2007-11-27 22:31         ` Phillip Susi

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=20071120011236.GA17420@redhat.com \
    --to=davej@redhat.com \
    --cc=Stephen.Clark@seclark.us \
    --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