diff options
| author | Eric Dumazet <[email protected]> | 2009-09-30 20:36:19 +0200 |
|---|---|---|
| committer | Ingo Molnar <[email protected]> | 2009-09-30 22:56:10 +0200 |
| commit | 152f9d0710a62708710161bce1b29fa8292c8c11 (patch) | |
| tree | 1a9fb02d236a0328a711eccdef9e29112e216ff7 /tools/perf/scripts/python/check-perf-trace.py | |
| parent | 79e1dd05d1a22e95ab6d54d21836f478b3b56976 (diff) | |
sched_clock: Fix atomicity/continuity bug by using cmpxchg64()
Commit def0a9b2573 (sched_clock: Make it NMI safe) assumed
cmpxchg() of 64bit values was available on X86_32.
That is not so - and causes some subtle scheduler misbehavior due
to incorrect timestamps off to up by ~4 seconds.
Two symptoms are known right now:
- interactivity problems seen by Arjan: up to 600 msecs
latencies instead of the expected 20-40 msecs. These
latencies are very visible on the desktop.
- incorrect CPU stats: occasionally too high percentages in 'top',
and crazy CPU usage stats.
Reported-by: Martin Schwidefsky <[email protected]>
Signed-off-by: Eric Dumazet <[email protected]>
Signed-off-by: Arjan van de Ven <[email protected]>
Acked-by: Linus Torvalds <[email protected]>
Cc: John Stultz <[email protected]>
Cc: Peter Zijlstra <[email protected]>
LKML-Reference: <[email protected]>
Signed-off-by: Ingo Molnar <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/check-perf-trace.py')
0 files changed, 0 insertions, 0 deletions