linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@linux.intel.com>
To: Thomas Renninger <trenn@suse.de>
Cc: Tiago Marques <tiagomnm@gmail.com>,
	discuss@lesswatts.org, linux-pm@lists.linux-foundation.org,
	cpufreq@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [Discuss] Speedstep on Celeron SU2300 - 20% more battery	lifetime on Windows
Date: Mon, 06 Sep 2010 08:47:28 -0700	[thread overview]
Message-ID: <4C850D10.2050801@linux.intel.com> (raw)
In-Reply-To: <201009061035.03727.trenn@suse.de>

  On 9/6/2010 1:35 AM, Thomas Renninger wrote:
> Hi,
>
> I am adding lesswatts.org and linux-pm list.
> I expect you found out why you do not get frequency/P- states and it
> seem to be correct. On these lists, people can help you further
> to find out Linux vs Windows battery drain differences.
>
> If you have the same backlight settings, I expect C-state or graphics
> card must be the reason. There is nothing else than CPU or GPU
> that drains so much energy for being the reason of
> 20% more battery life time.
> Which graphics card and driver do you use (for nvidia/ati, trying the
> binary one for comparison, might show a big difference on a recent
> card)?
> Which C-state driver do you use (there is an acpi and intel_idle one
> with latest kernels):
> cat /sys/devices/system/cpu/cpuidle/current_driver
> I hope to be able to provide a c-state tool soon, for now you have to
> go through:
> cat /sys/devices/system/cpu/cpu*/cpuidle/state*
> to check which and how often/efficient C-states are used.

powertop will tell you exactly this

(and the next version will provide much much more detail)



  reply	other threads:[~2010-09-06 15:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTiktJ5Xgnsmq2je7T3Yc5Sf53Bu8vWMM1XT1V_vm@mail.gmail.com>
     [not found] ` <201009020152.37466.trenn@suse.de>
     [not found]   ` <AANLkTi=WDEA+prG26g5R9oG1uZ7cNgaMrYDtug_LM7bY@mail.gmail.com>
     [not found]     ` <AANLkTi=WDEA+prG26g5R9oG1uZ7cNgaMrYDtug_LM7bY-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-09-06  8:35       ` Speedstep on Celeron SU2300 - 20% more battery lifetime on Windows Thomas Renninger
2010-09-06 15:47         ` Arjan van de Ven [this message]
2010-09-06 22:03           ` [Discuss] " Tiago Marques
2010-09-06 23:28             ` Arjan van de Ven
     [not found]               ` <4C85790A.50005-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2010-10-03 15:01                 ` Tiago Marques
     [not found]                   ` <AANLkTin5Kjiw+Z4F8Y+h+c0Qb_tu1o0SuwHEJ=R3iu40-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-10-03 15:03                     ` Tiago Marques
2010-09-06 21:47         ` Tiago Marques
2010-09-07 11:47           ` Thomas Renninger
2010-10-03 15:06             ` Tiago Marques
2010-09-07 15:22           ` Matthew Garrett
2010-09-07 16:43             ` Thomas Renninger
2010-10-03 15:56               ` Tiago Marques
2010-10-03 15:45             ` Tiago Marques
2010-09-07 16:20           ` Len Brown
2010-10-03 15:47             ` Tiago Marques

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=4C850D10.2050801@linux.intel.com \
    --to=arjan@linux.intel.com \
    --cc=cpufreq@vger.kernel.org \
    --cc=discuss@lesswatts.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=tiagomnm@gmail.com \
    --cc=trenn@suse.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;
as well as URLs for NNTP newsgroup(s).