http://defect.opensolaris.org/bz/show_bug.cgi?id=3838
Summary: Need to disable PM framework polling when PAD is enabled
Classification: Development
Product: power-mgmt
Version: unspecified
Platform: Other
OS/Version: Solaris
Status: ACCEPTED
Severity: normal
Priority: P3
Component: PAD
AssignedTo: eric.saxe at sun.com
ReportedBy: eric.saxe at sun.com
CC: tesla-dev at opensolaris.org
Estimated Hours: 0.0
With PAD, P-state transitions are driven by dispatcher events...however, while
these transitions are taking place, the PM framework and cpudrv are still
polling the utilization of the CPUs, and making P-state transitions as well.
When one mechanism is active, the other needs to be disabled.
Further, it would be nice if there was a way one could specify the preferred
mechanism.
Here's a proposal:
In power.conf, there is the cpupm keyword, where the syntax is:
cpupm behavior
Current acceptable behavior values and their meanings are :
enable CPU Power Management will be started when this
entry is encountered.
disable CPU Power Management will be stopped when this
entry is encountered.
We could add two additional behaviors the allow one to explicitly express the
desired mechanism:
event-mode CPU Power Management will be started when this
entry is encountered, and CPU power state transitions
will be driven by thread scheduler/dispatcher events.
The cpu-threshold, and system-threshold directives are
not used for CPUs in this mode.
polled-mode CPU Power Management will be started when this
entry is encountered. The Power Management framework
will poll the idleness of the system's CPUs, and will
manage their power once idle for the period of time
specified by either the system-threshold or cpu-threshold.
In this case, "cpupm enable" would enable CPU power management, using the
system's default mechanism (likely event-mode), and cpupm disable would disable
CPU power management all together.
Comments on this proposal are most welcome. :)
--
Configure bugmail: http://defect.opensolaris.org/bz/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
