diff options
author | Valentin Schneider <valentin.schneider@arm.com> | 2020-08-17 12:29:56 +0100 |
---|---|---|
committer | Ingo Molnar <mingo@kernel.org> | 2020-08-19 10:49:49 +0200 |
commit | c200191d4c2c1aa2ffb62a984b756ac1f02dc55c (patch) | |
tree | 23b960dd43e9050577d00ea337abc0b15e284b22 /tools/io_uring | |
parent | ab65afb094c7b2e954e8d56ffbc7df843211c2c8 (diff) | |
download | linux-c200191d4c2c1aa2ffb62a984b756ac1f02dc55c.tar.bz2 |
sched/topology: Propagate SD_ASYM_CPUCAPACITY upwards
We currently set this flag *only* on domains whose topology level exactly
match the level where we detect asymmetry (as returned by
asym_cpu_capacity_level()). This is rather problematic.
Say there are two clusters in the system, one with a lone big CPU and the
other with a mix of big and LITTLE CPUs (as is allowed by DynamIQ):
DIE [ ]
MC [ ][ ]
0 1 2 3 4
L L B B B
asym_cpu_capacity_level() will figure out that the MC level is the one
where all CPUs can see a CPU of max capacity, and we will thus set
SD_ASYM_CPUCAPACITY at MC level for all CPUs.
That lone big CPU will degenerate its MC domain, since it would be alone in
there, and will end up with just a DIE domain. Since the flag was only set
at MC, this CPU ends up not seeing any SD with the flag set, which is
broken.
Rather than clearing dflags at every topology level, clear it before
entering the topology level loop. This will properly propagate upwards
flags that are set starting from a certain level.
Signed-off-by: Valentin Schneider <valentin.schneider@arm.com>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Reviewed-by: Quentin Perret <qperret@google.com>
Reviewed-by: Dietmar Eggemann <dietmar.eggemann@arm.com>
Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Link: https://lore.kernel.org/r/20200817113003.20802-11-valentin.schneider@arm.com
Diffstat (limited to 'tools/io_uring')
0 files changed, 0 insertions, 0 deletions