diff options
| author |   Rik van Riel <riel@surriel.com> | 2024-07-15 13:49:41 -0400 |
|---|---|---|
| committer |   Neeraj Upadhyay <neeraj.upadhyay@kernel.org> | 2024-08-15 00:06:48 +0530 |
| commit | 9fbaa44114ca6b69074a488295e86a9fa7e685f9 (patch) | |
| tree | 18da76d874fe7db6bbe10cf3100f2d3ee3e9f58c /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | locking/csd-lock: Use backoff for repeated reports of same incident (diff) | |
| download | wireguard-linux-9fbaa44114ca6b69074a488295e86a9fa7e685f9.tar.xz wireguard-linux-9fbaa44114ca6b69074a488295e86a9fa7e685f9.zip | |
smp: print only local CPU info when sched_clock goes backward
About 40% of all csd_lock warnings observed in our fleet appear to
be due to sched_clock() going backward in time (usually only a little
bit), resulting in ts0 being larger than ts2.
When the local CPU is at fault, we should print out a message reflecting
that, rather than trying to get the remote CPU's stack trace.
Signed-off-by: Rik van Riel <riel@surriel.com>
Tested-by: "Paul E. McKenney" <paulmck@kernel.org>
Signed-off-by: Neeraj Upadhyay <neeraj.upadhyay@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions