diff options
| author | Rohit Gupta <rohgup@codeaurora.org> | 2018-05-29 17:23:04 +0200 |
|---|---|---|
| committer | Georg Veichtlbauer <georg@vware.at> | 2023-07-26 21:01:08 +0200 |
| commit | 821cf3a1a8476001f02a27771dcd27ef8b913feb (patch) | |
| tree | 4449b2c129d09812d864d495bf8eaad44df7a248 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | 9f52618d15b8c2461ad3ade8440a2ac1e21d203c (diff) | |
BACKPORT: cpufreq: schedutil: Cache tunables on governor exit
Currently when all the related CPUs from a policy go offline or the
governor is switched, cpufreq framework calls sugov_exit() that
frees the governor tunables. When any of the related CPUs comes back
online or governor is switched back to schedutil sugov_init() gets
called which allocates a fresh set of tunables that are set to
default values. This can cause the userspace settings to those
tunables to be lost across governor switches or when an entire
cluster is hotplugged out.
To prevent this, save the tunable values on governor exit. Restore
these values to the newly allocated tunables on governor init.
Change-Id: I671d4d0e1a4e63e948bfddb0005367df33c0c249
Signed-off-by: Rohit Gupta <rohgup@codeaurora.org>
[Caching and restoring different tunables.]
Signed-off-by: joshuous <joshuous@gmail.com>
Change-Id: I852ae2d23f10c9337e7057a47adcc46fe0623c6a
Signed-off-by: joshuous <joshuous@gmail.com>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions