Thomas Gleixner 07454bfff1 clockevents: check broadcast tick device not the clock events device ...

Impact: jiffies increment too fast.

Hugh Dickins noted that with NOHZ=n and HIGHRES=n jiffies get
incremented too fast. The reason is a wrong check in the broadcast
enter/exit code, which keeps the local apic timer in periodic mode
when the switch happens.

Signed-off-by: Thomas Gleixner <[email protected]>

2008-10-04 10:51:07 +02:00

..

clockevents.c

clockevents: make device shutdown robust

2008-09-16 13:47:02 -07:00

clocksource.c

Merge branch 'cpus4096-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip

2008-07-23 18:37:44 -07:00

jiffies.c

…

Kconfig

…

Makefile

…

ntp.c

ntp: fix calculation of the next jiffie to trigger RTC sync

2008-09-06 15:31:48 +02:00

tick-broadcast.c

clockevents: check broadcast tick device not the clock events device

2008-10-04 10:51:07 +02:00

tick-common.c

clockevents: prevent mode mismatch on cpu online

2008-09-23 11:38:53 +02:00

tick-internal.h

timers: fix build error in !oneshot case

2008-09-23 12:57:00 +02:00

tick-oneshot.c

clockevents: remove WARN_ON which was used to gather information

2008-09-09 22:20:01 +02:00

tick-sched.c

hrtimer: prevent migration of per CPU hrtimers

2008-09-29 17:09:14 +02:00

timekeeping.c

…

timer_list.c

…

timer_stats.c

…