diff options
| author | Alex Shi <alex.shi@linaro.org> | 2017-01-12 21:27:03 +0800 |
|---|---|---|
| committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2017-01-30 11:05:29 +0100 |
| commit | 37efa4b41ffb31dcdfc3beb97d47992bb2a083e5 (patch) | |
| tree | b0349aa9ebf511ac64c0060d7d852111f0968002 /drivers/misc/vmw_vmci | |
| parent | 9908859acaa95640d4a07991a93f7cd5bfc18e02 (diff) | |
| download | talos-op-linux-37efa4b41ffb31dcdfc3beb97d47992bb2a083e5.tar.gz talos-op-linux-37efa4b41ffb31dcdfc3beb97d47992bb2a083e5.zip | |
CPU / PM: expose pm_qos_resume_latency for CPUs
The cpu-dma PM QoS constraint impacts all the cpus in the system. There
is no way to let the user to choose a PM QoS constraint per cpu.
The following patch exposes to the userspace a per cpu based sysfs file
in order to let the userspace to change the value of the PM QoS latency
constraint.
This change is inoperative in its form and the cpuidle governors have to
take into account the per cpu latency constraint in addition to the
global cpu-dma latency constraint in order to operate properly.
BTW
The pm_qos_resume_latency usage defined in
Documentation/ABI/testing/sysfs-devices-power
The /sys/devices/.../power/pm_qos_resume_latency_us attribute
contains the PM QoS resume latency limit for the given device,
which is the maximum allowed time it can take to resume the
device, after it has been suspended at run time, from a resume
request to the moment the device will be ready to process I/O,
in microseconds. If it is equal to 0, however, this means that
the PM QoS resume latency may be arbitrary.
Signed-off-by: Alex Shi <alex.shi@linaro.org>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'drivers/misc/vmw_vmci')
0 files changed, 0 insertions, 0 deletions
