diff options
| author | Viresh Kumar <[email protected]> | 2015-06-10 02:20:23 +0200 |
|---|---|---|
| committer | Rafael J. Wysocki <[email protected]> | 2015-06-11 01:02:45 +0200 |
| commit | 9591becbf226e3aa0f6c73494736e2c5ab14cc8d (patch) | |
| tree | 045117d2fbb058e73f7679fc2b7140e9c3ec8f9d /tools/perf/scripts/python/event_analyzing_sample.py | |
| parent | 3654c5cc810e9b1f7eadf19780d1bc5f37e1ae6e (diff) | |
cpufreq: Restart governor as soon as possible
__cpufreq_remove_dev_finish() is doing two things today:
- Restarts the governor if some CPUs from concerned policy are still
online.
- Frees the policy if all CPUs are offline.
The first task of restarting the governor can be moved to
__cpufreq_remove_dev_prepare() to restart the governor early. There is
no race between _prepare() and _finish() as they would be handling
completely different cases. _finish() will only be required if we are
going to free the policy and that has nothing to do with restarting the
governor.
Original-by: Saravana Kannan <[email protected]>
Signed-off-by: Viresh Kumar <[email protected]>
Signed-off-by: Rafael J. Wysocki <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/event_analyzing_sample.py')
0 files changed, 0 insertions, 0 deletions