summaryrefslogtreecommitdiffstats
path: root/drivers/leds
diff options
context:
space:
mode:
authorEric Dumazet2009-09-30 20:36:19 +0200
committerIngo Molnar2009-09-30 22:56:10 +0200
commit152f9d0710a62708710161bce1b29fa8292c8c11 (patch)
tree1a9fb02d236a0328a711eccdef9e29112e216ff7 /drivers/leds
parentx86: Provide an alternative() based cmpxchg64() (diff)
downloadkernel-qcow2-linux-152f9d0710a62708710161bce1b29fa8292c8c11.tar.gz
kernel-qcow2-linux-152f9d0710a62708710161bce1b29fa8292c8c11.tar.xz
kernel-qcow2-linux-152f9d0710a62708710161bce1b29fa8292c8c11.zip
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 <schwidefsky@de.ibm.com> Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com> Signed-off-by: Arjan van de Ven <arjan@linux.intel.com> Acked-by: Linus Torvalds <torvalds@linux-foundation.org> Cc: John Stultz <johnstul@us.ibm.com> Cc: Peter Zijlstra <a.p.zijlstra@chello.nl> LKML-Reference: <20090930170754.0886ff2e@infradead.org> Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'drivers/leds')
0 files changed, 0 insertions, 0 deletions