diff options
author | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2016-02-18 02:26:55 +0100 |
---|---|---|
committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2016-03-09 14:41:08 +0100 |
commit | a33cce1c6cc3268d8b4843bf1e4ac1e70b27d107 (patch) | |
tree | efeb3572a7cf740e4b521ac2d68218c6b7ae79ef /Documentation/spi | |
parent | 76c5f66aa10720a377dfe8beebd39a0b2a938965 (diff) | |
download | op-kernel-dev-a33cce1c6cc3268d8b4843bf1e4ac1e70b27d107.zip op-kernel-dev-a33cce1c6cc3268d8b4843bf1e4ac1e70b27d107.tar.gz |
cpufreq: governor: Fix CPU load information updates via ->store
The ->store() callbacks of some tunable sysfs attributes of the
ondemand and conservative governors trigger immediate updates of
the CPU load information for all CPUs "governed" by the given
dbs_data by walking the cpu_dbs_info structures for all online
CPUs in the system and updating them.
This is questionable for two reasons. First, it may lead to a lot of
extra overhead on a system with many CPUs if the given dbs_data is
only associated with a few of them. Second, if governor tunables are
per-policy, the CPUs associated with the other sets of governor
tunables should not be updated.
To address this issue, use the observation that in all of the places
in question the update operation may be carried out in the same way
(because all of the tunables involved are now located in struct
dbs_data and readily available to the common code) and make the
code in those places invoke the same (new) helper function that
will carry out the update correctly.
That new function always checks the ignore_nice_load tunable value
and updates the CPUs' prev_cpu_nice data fields if that's set, which
wasn't done by the original code in store_io_is_busy(), but it
should have been done in there too.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Diffstat (limited to 'Documentation/spi')
0 files changed, 0 insertions, 0 deletions