diff options
| author | Viresh Kumar <[email protected]> | 2017-03-21 11:36:06 +0530 |
|---|---|---|
| committer | Rafael J. Wysocki <[email protected]> | 2017-03-22 02:38:27 +0100 |
| commit | ff010472fb75670cb5c08671e820eeea3af59c87 (patch) | |
| tree | f82f32db99ebc5cd9c5f2b8d67c3fec364c519f7 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | 9b4f603e7a9f4282aec451063ffbbb8bb410dcd9 (diff) | |
cpufreq: Restore policy min/max limits on CPU online
On CPU online the cpufreq core restores the previous governor (or
the previous "policy" setting for ->setpolicy drivers), but it does
not restore the min/max limits at the same time, which is confusing,
inconsistent and real pain for users who set the limits and then
suspend/resume the system (using full suspend), in which case the
limits are reset on all CPUs except for the boot one.
Fix this by making cpufreq_online() restore the limits when an inactive
policy is brought online.
The commit log and patch are inspired from Rafael's earlier work.
Reported-by: Rafael J. Wysocki <[email protected]>
Signed-off-by: Viresh Kumar <[email protected]>
Cc: 4.3+ <[email protected]> # 4.3+
Signed-off-by: Rafael J. Wysocki <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions