diff options
| author | Steve Muckle <steve.muckle@linaro.org> | 2016-08-26 21:40:47 +0300 |
|---|---|---|
| committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2016-09-01 01:32:57 +0300 |
| commit | 8314bc83f6a33958a033955e9bdc48e8dd4d5fb0 (patch) | |
| tree | 123b8124e4e740e85152bed5602788b06f6a89ad /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | 12bde33dbb3eadd60343a8a71c39766073c1d752 (diff) | |
| download | linux-8314bc83f6a33958a033955e9bdc48e8dd4d5fb0.tar.xz | |
cpufreq / sched: ignore SMT when determining max cpu capacity
PELT does not consider SMT when scaling its utilization values via
arch_scale_cpu_capacity(). The value in rq->cpu_capacity_orig does
take SMT into consideration though and therefore may be smaller than
the utilization reported by PELT.
On an Intel i7-3630QM for example rq->cpu_capacity_orig is 589 but
util_avg scales up to 1024. This means that a 50% utilized CPU will show
up in schedutil as ~86% busy.
Fix this by using the same CPU scaling value in schedutil as that which
is used by PELT.
Signed-off-by: Steve Muckle <smuckle@linaro.org>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions