diff options
author | Viresh Kumar <[email protected]> | 2021-01-08 16:46:51 +0530 |
---|---|---|
committer | Will Deacon <[email protected]> | 2021-01-20 12:49:40 +0000 |
commit | 384e5699e101b1ee184590a39ee60f10ec0d36b6 (patch) | |
tree | 3661320231187739860e0e459cd6b50e7f27e50b /tools/perf/scripts/python/export-to-postgresql.py | |
parent | 19c329f6808995b142b3966301f217c831e7cf31 (diff) |
arm64: topology: Avoid the have_policy check
Every time I have stumbled upon this routine, I get confused with the
way 'have_policy' is used and I have to dig in to understand why is it
so. Here is an attempt to make it easier to understand, and hopefully it
is an improvement.
The 'have_policy' check was just an optimization to avoid writing
to amu_fie_cpus in case we don't have to, but that optimization itself
is creating more confusion than the real work. Lets just do that if all
the CPUs support AMUs. It is much cleaner that way.
Reviewed-by: Ionela Voinescu <[email protected]>
Signed-off-by: Viresh Kumar <[email protected]>
Tested-by: Ionela Voinescu <[email protected]>
Link: https://lore.kernel.org/r/c125766c4be93461772015ac7c9a6ae45d5756f6.1610104461.git.viresh.kumar@linaro.org
Signed-off-by: Will Deacon <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions