Wang, Jedy wrote: > >Hi Li, > >As far as I know, gnome-power-manager has removed the support for >changing governor which is the same as profile I think. I remember >someone wrote a blog explaining the reason but I can not find it now. I >wonder why what makes us still need to implement this feature.
To make the different requirements happy. Mostly, we have default balanced policy to optimize perf/power ratio. But, some users want to drive the system to the max performance at any energy cost, while some users want to prolong their battery life and less heat, less noise, like the following one: http://opensolaris.org/jive/thread.jspa?messageID=425851 You know, performance and power are always in the opposite direction. I'd like to propose the user profile support to enhance solaris pm. > >I remember why already support 2 profile through gnome-power-manager on >Solaris. What's the difference between them? Anup probably knows the details, but from what I know, it doesn't work. > >I do not understand the exact meaning perf-bias, balanced and power-bias >either. Does not perf-bias means the cpu frequency will be always at the >highest level? Currently, Intel processor has a few pm features(Turbo, Speedstep, Deeper cstate), Solaris also has a few power related implementation. Besides the highest frequency, Perf-bias bias means the shallow idle state(deeper c-state causes long wakeup latency), load balance thread dispatcher, balanced interrupt routing policy, etc. However, if the user needs max power saving, the policies mentioned above can be adjusted to match this request if we have the user profile support. Does this make sense? Thanks, -Aubrey > >Regards, > >Jedy >On Wed, 2009-11-04 at 08:47 +0800, Li, Aubrey wrote: >> Hi, >> >> When we enable intel energy performance bias feature, we found the power >> profile implementation is necessary. Here I did a draft for cpu level power >> policy. >> http://cr.opensolaris.org/~aubrey/cpu_power_policy_v1/ >> >> The proposal added a new keyword to /etc/power.conf >> "cpu-power-policy", >> >> And we have 4 options for this new keyword: >> 1) perf-bias >> 2) balanced >> 3) power-bias >> 4) default, the same as perf-bias. >> >> /etc/power.conf accepts the user input and passes the prefered policy >> to the kernel thru ioctl. Then pm_ioctl calls the callback to walk a cpu >> power policy list. Every cpu pm feature which wants to be adjusted by >> this option and verified to be supported will register its callback function >> to the list, so that it can be called and adjusted by pmconfig. >> -------------------------------------------------------- >> /etc/power.conf >> | >> pm_ioctl(cpu_power_policy, policy) >> | >> cpu_power_policy_callb (policy) >> | >> ----> registered pm feature callback 1 (ENERGY_PERF_BIAS) >> | >> ----> registered pm feature callback 2 >> ... >> --------------------------------------------------------- >> Currently, only energy_perf_bias feature is registered, because my intention >> is >> to support adjusting energy_perf_bias MSR without reboot. I guess we probably >> can add p/t/c-state support later. When we add p/t/c-state support, my quick >> thought is, this option will override "cpupm" and "cpu-deep-idle" setting. >> >> Welcome your any comments and suggestions. >> >> Thanks, >> -Aubrey >> _______________________________________________ >> pm-discuss mailing list >> pm-discuss at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/pm-discuss >
