summaryrefslogtreecommitdiffstats
path: root/arch/powerpc/xmon
diff options
context:
space:
mode:
authorArjan van de Ven <arjan@infradead.org>2009-10-08 06:40:41 -0700
committerIngo Molnar <mingo@elte.hu>2009-10-08 17:27:27 +0200
commit9bcbdd9c58617f1301dd4f17c738bb9bc73aca70 (patch)
tree26c4e1faae64c3352c909f13a6c04ee3c68a99ed /arch/powerpc/xmon
parentfdc6f192e7e1ae80565af23cc33dc88e3dcdf184 (diff)
downloadblackbird-obmc-linux-9bcbdd9c58617f1301dd4f17c738bb9bc73aca70.tar.gz
blackbird-obmc-linux-9bcbdd9c58617f1301dd4f17c738bb9bc73aca70.zip
x86, timers: Check for pending timers after (device) interrupts
Now that range timers and deferred timers are common, I found a problem with these using the "perf timechart" tool. Frans Pop also reported high scheduler latencies via LatencyTop, when using iwlagn. It turns out that on x86, these two 'opportunistic' timers only get checked when another "real" timer happens. These opportunistic timers have the objective to save power by hitchhiking on other wakeups, as to avoid CPU wakeups by themselves as much as possible. The change in this patch runs this check not only at timer interrupts, but at all (device) interrupts. The effect is that: 1) the deferred timers/range timers get delayed less 2) the range timers cause less wakeups by themselves because the percentage of hitchhiking on existing wakeup events goes up. I've verified the working of the patch using "perf timechart", the original exposed bug is gone with this patch. Frans also reported success - the latencies are now down in the expected ~10 msec range. Signed-off-by: Arjan van de Ven <arjan@linux.intel.com> Tested-by: Frans Pop <elendil@planet.nl> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Mike Galbraith <efault@gmx.de> LKML-Reference: <20091008064041.67219b13@infradead.org> Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'arch/powerpc/xmon')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud