diff options
author | Peter Zijlstra <[email protected]> | 2021-08-19 13:09:17 +0200 |
---|---|---|
committer | Peter Zijlstra <[email protected]> | 2021-08-20 12:32:53 +0200 |
commit | 3c474b3239f12fe0b00d7e82481f36a1f31e79ab (patch) | |
tree | 581925bf416438a0e686d4dc21e4a965d8c5b348 /lib/debugobjects.c | |
parent | 7c60610d476766e128cc4284bb6349732cbd6606 (diff) |
sched: Fix Core-wide rq->lock for uninitialized CPUs
Eugene tripped over the case where rq_lock(), as called in a
for_each_possible_cpu() loop came apart because rq->core hadn't been
setup yet.
This is a somewhat unusual, but valid case.
Rework things such that rq->core is initialized to point at itself. IOW
initialize each CPU as a single threaded Core. CPU online will then join
the new CPU (thread) to an existing Core where needed.
For completeness sake, have CPU offline fully undo the state so as to
not presume the topology will match the next time it comes online.
Fixes: 9edeaea1bc45 ("sched: Core-wide rq->lock")
Reported-by: Eugene Syromiatnikov <[email protected]>
Signed-off-by: Peter Zijlstra (Intel) <[email protected]>
Reviewed-by: Josh Don <[email protected]>
Tested-by: Eugene Syromiatnikov <[email protected]>
Link: https://lkml.kernel.org/r/[email protected]
Diffstat (limited to 'lib/debugobjects.c')
0 files changed, 0 insertions, 0 deletions