diff options
author | Jason Low <[email protected]> | 2014-04-28 15:45:54 -0700 |
---|---|---|
committer | Ingo Molnar <[email protected]> | 2014-05-07 11:51:36 +0200 |
commit | 0e5b5337f0da073e1f17aec3c322ea7826975d0d (patch) | |
tree | 3f47f8935bb09d489614f5d86421c84f92a40e73 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
parent | 6ccdc84b81a0a6c09a7f0427761d2f8cecfc2218 (diff) |
sched: Fix updating rq->max_idle_balance_cost and rq->next_balance in idle_balance()
The following commit:
e5fc66119ec9 ("sched: Fix race in idle_balance()")
can potentially cause rq->max_idle_balance_cost to not be updated,
even when load_balance(NEWLY_IDLE) is attempted and the per-sd
max cost value is updated.
Preeti noticed a similar issue with updating rq->next_balance.
In this patch, we fix this by making sure we still check/update those values
even if a task gets enqueued while browsing the domains.
Signed-off-by: Jason Low <[email protected]>
Reviewed-by: Preeti U Murthy <[email protected]>
Signed-off-by: Peter Zijlstra <[email protected]>
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Link: http://lkml.kernel.org/r/[email protected]
Signed-off-by: Ingo Molnar <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions