public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Jason Chagas <jason.chagas@gmail.com>
Cc: Linux Power Management List <linux-pm@lists.osdl.org>
Subject: Re: RFC: /sys/power/policy_preference
Date: Thu, 17 Jun 2010 14:44:41 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.00.1006171441160.4214@localhost.localdomain> (raw)
In-Reply-To: <AANLkTinVfSUnR5cAvNowtzg8WEgm0JroN1EiaWAd2iHB@mail.gmail.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 749 bytes --]

On Wed, 16 Jun 2010, Jason Chagas wrote:

> > powersave (can sacrifice measurable performance)
> >        scheduler: enable sched_smt_power_savings
> >        cpuidle: enable all C-states, subject to QOS
> >        ondemand: disable turbo mode, powersave_bias=10
> >        msr_ia32_energy_perf_bias: 11 of 15
> >
> 
> Do you have any pointers to info (or code) on how the different
> C&P-states are selected within each level?

I'm not proposing any changes to how the cpuidle menu govenor
selects C-states, or how it obeys PM_QOS, except for 1 thing.

I am proposing that in "max_performance" mode that C-states
be disabled entirely, to avoid any state latency whatsoever.

thanks,
Len Brown, Intel Open Source Technology Center

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2010-06-17 18:44 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-16 21:05 RFC: /sys/power/policy_preference Len Brown
2010-06-16 22:12 ` Jason Chagas
2010-06-17 18:44   ` Len Brown [this message]
2010-06-17  6:03 ` [linux-pm] " Igor.Stoppa
2010-06-17 19:00   ` Len Brown
2010-06-17 16:14 ` Victor Lowther
2010-06-17 19:02   ` Len Brown
2010-06-17 22:23     ` Victor Lowther
2010-06-18  5:56       ` Len Brown
2010-06-18 11:55         ` Victor Lowther
2010-06-19 15:17   ` Vaidyanathan Srinivasan
2010-06-19 19:04     ` Rafael J. Wysocki
2010-06-17 20:48 ` Mike Chan
2010-06-18  6:25   ` Len Brown
2010-06-21 20:10 ` [linux-pm] " Dipankar Sarma
2010-09-28 16:17 ` x86_energy_perf_policy.c Len Brown
2010-10-23  4:40   ` [PATCH] tools: add x86_energy_perf_policy to program MSR_IA32_ENERGY_PERF_BIAS Len Brown
     [not found]   ` <alpine.LFD.2.00.1010230035360.29399@localhost.localdomain>
2010-10-27  3:23     ` Andrew Morton
     [not found]     ` <20101026202307.c028e26c.akpm@linux-foundation.org>
2010-10-27  6:01       ` Ingo Molnar
     [not found]       ` <20101027060139.GB5603@elte.hu>
2010-10-27 11:43         ` Arnaldo Carvalho de Melo
2010-11-15 16:07     ` [PATCH RESEND] tools: add power/x86/x86_energy_perf_policy " Len Brown
     [not found]     ` <alpine.LFD.2.00.1011151103280.2939@x980>
2010-11-17 11:35       ` Andi Kleen
     [not found]       ` <8739r0rxlz.fsf@basil.nowhere.org>
2010-11-22 20:13         ` Len Brown
     [not found]         ` <alpine.LFD.2.00.1011221348200.19247@x980>
2010-11-22 20:33           ` Andi Kleen
     [not found]           ` <20101122203359.GD21836@basil.fritz.box>
2010-11-23  4:48             ` Len Brown
2010-11-24  5:31       ` [PATCH v2] tools: create power/x86/x86_energy_perf_policy Len Brown
     [not found]       ` <alpine.LFD.2.00.1011240028470.20657@x980>
2010-11-25  5:52         ` Chen Gong
     [not found]         ` <4CEDF9BB.9030002@linux.intel.com>
2010-11-25  8:59           ` Chen Gong

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=alpine.LFD.2.00.1006171441160.4214@localhost.localdomain \
    --to=lenb@kernel.org \
    --cc=jason.chagas@gmail.com \
    --cc=linux-pm@lists.osdl.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