summaryrefslogtreecommitdiff
path: root/drivers/rtc
diff options
context:
space:
mode:
authorJeff Ohlstein <johlstei@codeaurora.org>2011-11-18 15:47:10 -0800
committerThomas Gleixner <tglx@linutronix.de>2011-11-19 12:17:37 +0100
commit27c9cd7e601632b3794e1c3344d37b86917ffb43 (patch)
treedc6f3d9accdf9c7fd8fd80dd81ff2ed7e07304e7 /drivers/rtc
parentd004e024058a0eaca097513ce62cbcf978913e0a (diff)
downloadlinux-3.10-27c9cd7e601632b3794e1c3344d37b86917ffb43.tar.gz
linux-3.10-27c9cd7e601632b3794e1c3344d37b86917ffb43.tar.bz2
linux-3.10-27c9cd7e601632b3794e1c3344d37b86917ffb43.zip
hrtimer: Fix extra wakeups from __remove_hrtimer()
__remove_hrtimer() attempts to reprogram the clockevent device when the timer being removed is the next to expire. However, __remove_hrtimer() reprograms the clockevent *before* removing the timer from the timerqueue and thus when hrtimer_force_reprogram() finds the next timer to expire it finds the timer we're trying to remove. This is especially noticeable when the system switches to NOHz mode and the system tick is removed. The timer tick is removed from the system but the clockevent is programmed to wakeup in another HZ anyway. Silence the extra wakeup by removing the timer from the timerqueue before calling hrtimer_force_reprogram() so that we actually program the clockevent for the next timer to expire. This was broken by 998adc3 "hrtimers: Convert hrtimers to use timerlist infrastructure". Signed-off-by: Jeff Ohlstein <johlstei@codeaurora.org> Cc: stable@vger.kernel.org Link: http://lkml.kernel.org/r/1321660030-8520-1-git-send-email-johlstei@codeaurora.org Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Diffstat (limited to 'drivers/rtc')
0 files changed, 0 insertions, 0 deletions