diff options
author | Ionela Voinescu <[email protected]> | 2022-07-04 11:16:01 +0100 |
---|---|---|
committer | Sudeep Holla <[email protected]> | 2022-07-04 16:23:16 +0100 |
commit | bfcc4397435dc0407099b9a805391abc05c2313b (patch) | |
tree | 0ec3b4355558ce3bfb77ef0bb988077ca39a27c1 /tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace/EventClass.py | |
parent | 26a2b73a7b15a51ec1409648c9b43882f66fbacf (diff) |
arch_topology: Limit span of cpu_clustergroup_mask()
Currently the cluster identifier is not set on DT based platforms.
The reset or default value is -1 for all the CPUs. Once we assign the
cluster identifier values correctly, the cluster_sibling mask will be
populated and returned by cpu_clustergroup_mask() to contribute in the
creation of the CLS scheduling domain level, if SCHED_CLUSTER is
enabled.
To avoid topologies that will result in questionable or incorrect
scheduling domains, impose restrictions regarding the span of clusters,
as presented to scheduling domains building code: cluster_sibling should
not span more or the same CPUs as cpu_coregroup_mask().
This is needed in order to obtain a strict separation between the MC and
CLS levels, and maintain the same domains for existing platforms in
the presence of CONFIG_SCHED_CLUSTER, where the new cluster information
is redundant and irrelevant for the scheduler.
While previously the scheduling domain builder code would have removed MC
as redundant and kept CLS if SCHED_CLUSTER was enabled and the
cpu_coregroup_mask() and cpu_clustergroup_mask() spanned the same CPUs,
now CLS will be removed and MC kept.
Link: https://lore.kernel.org/r/[email protected]
Cc: Darren Hart <[email protected]>
Tested-by: Conor Dooley <[email protected]>
Acked-by: Vincent Guittot <[email protected]>
Signed-off-by: Ionela Voinescu <[email protected]>
Signed-off-by: Sudeep Holla <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace/EventClass.py')
0 files changed, 0 insertions, 0 deletions