diff options
author | Peter Zijlstra <[email protected]> | 2017-02-02 16:55:06 +0100 |
---|---|---|
committer | Ingo Molnar <[email protected]> | 2017-02-24 08:58:33 +0100 |
commit | 8cb68b343a66cf19834472012590490d34d31703 (patch) | |
tree | 9fb6c71ddb2c046c0aaceb748248d94cc74a351d /tools/perf/scripts/python/call-graph-from-postgresql.py | |
parent | 2bfe01eff4307409b95859e860261d0907149b61 (diff) |
sched/core: Fix update_rq_clock() splat on hotplug (and suspend/resume)
The hotplug code still triggers the warning about using a stale
rq->clock value.
Fix things up to actually run update_rq_clock() in a place where we
record the 'UPDATED' flag, and then modify the annotation to retain
this flag over the rq->lock fiddling that happens as a result of
actually migrating all the tasks elsewhere.
Reported-by: Linus Torvalds <[email protected]>
Tested-by: Mike Galbraith <[email protected]>
Tested-by: Sachin Sant <[email protected]>
Tested-by: Borislav Petkov <[email protected]>
Signed-off-by: Peter Zijlstra (Intel) <[email protected]>
Reviewed-by: Matt Fleming <[email protected]>
Cc: Michael Ellerman <[email protected]>
Cc: Peter Zijlstra <[email protected]>
Cc: Ross Zwisler <[email protected]>
Cc: Thomas Gleixner <[email protected]>
Fixes: 4d25b35ea372 ("sched/fair: Restore previous rq_flags when migrating tasks in hotplug")
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