Re: [Dynamicpower-devel] DPM review

[Todd P. <tp...@mv...>]

Livio Tenze wrote:

> You sed me that " the dpm_set_os function which is placed in the idle 
> loop and scheduler by default": but does the standard implementation 
> (the standard code) exploit operating states different from "idle" and 
> "task"? In other words: in my montavista kernel I have 13 states: relock 
> idle-task idle sleep task-4 task-3 task-2 task-1 task task+1 task+2 
> task+3 task+4. Are these states exploited by the linux standard kernel 
> or new dpm_set_os calls are needed to use all these states? If new calls 
> are needed: which states are used by default?
> When you say that it is necessary to "and add dpm_set_os in the right 
> place to trigger the transition": do you mean in an external program 
> (e.g. in a dpm manager), into the applications code (if I am not wrong 
> these applications are labeled ad power-aware into the documentation I 
> read) or directly in the kernel code?
> Do you know whether a power manager implementation (to manage the 
> policies) does exist?

DPM provides the needed dpm_set_os() calls in the kernel.  You can 
modify your apps to set their own task states as needed, or use the 
default, or manage task states from an external program.  The power 
policy manager would typically set policies and other chores such as 
trigger system suspends.  I'm not aware of GPL'ed power managers hooked 
up to DPM.

-- 
Todd