diff options
author | Peter Zijlstra <a.p.zijlstra@chello.nl> | 2009-11-25 13:31:39 +0100 |
---|---|---|
committer | Ingo Molnar <mingo@elte.hu> | 2009-12-06 21:10:56 +0100 |
commit | 6ad4c18884e864cf4c77f9074d3d1816063f99cd (patch) | |
tree | f09643f6148b576fa2d23bf7d4b37d082d94e267 /kernel/kallsyms.c | |
parent | e1b8090bdf125f8b2e192149547fead7f302a89c (diff) | |
download | kernel_samsung_crespo-6ad4c18884e864cf4c77f9074d3d1816063f99cd.zip kernel_samsung_crespo-6ad4c18884e864cf4c77f9074d3d1816063f99cd.tar.gz kernel_samsung_crespo-6ad4c18884e864cf4c77f9074d3d1816063f99cd.tar.bz2 |
sched: Fix balance vs hotplug race
Since (e761b77: cpu hotplug, sched: Introduce cpu_active_map and redo
sched domain managment) we have cpu_active_mask which is suppose to rule
scheduler migration and load-balancing, except it never (fully) did.
The particular problem being solved here is a crash in try_to_wake_up()
where select_task_rq() ends up selecting an offline cpu because
select_task_rq_fair() trusts the sched_domain tree to reflect the
current state of affairs, similarly select_task_rq_rt() trusts the
root_domain.
However, the sched_domains are updated from CPU_DEAD, which is after the
cpu is taken offline and after stop_machine is done. Therefore it can
race perfectly well with code assuming the domains are right.
Cure this by building the domains from cpu_active_mask on
CPU_DOWN_PREPARE.
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
LKML-Reference: <new-submission>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'kernel/kallsyms.c')
0 files changed, 0 insertions, 0 deletions