diff options
author | Viresh Kumar <[email protected]> | 2015-07-18 11:30:59 +0530 |
---|---|---|
committer | Rafael J. Wysocki <[email protected]> | 2015-07-21 01:12:01 +0200 |
commit | 44152cb82d1ad6ae6f8b47c5437f6f1e65ca82c4 (patch) | |
tree | d4a0d3058f60345d6ae6bee7fdcc881fe0df690b /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | 42994af63cd1aafc9289035cf621e501b08732e9 (diff) |
cpufreq: governor: Keep single copy of information common to policy->cpus
Some information is common to all CPUs belonging to a policy, but are
kept on per-cpu basis. Lets keep that in another structure common to all
policy->cpus. That will make updates/reads to that less complex and less
error prone.
The memory for cpu_common_dbs_info is allocated/freed at INIT/EXIT, so
that it we don't reallocate it for STOP/START sequence. It will be also
be used (in next patch) while the governor is stopped and so must not be
freed that early.
Reviewed-and-tested-by: Preeti U Murthy <[email protected]>
Signed-off-by: Viresh Kumar <[email protected]>
Signed-off-by: Rafael J. Wysocki <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions