Thomas Gleixner 9c17bcda99 clockevents: prevent multiple init/shutdown ... While chasing the C1E/HPET bugreports I went through the clock events code inch by inch and found that the broadcast device can be initialized and shutdown multiple times. Multiple shutdowns are not critical, but useless waste of time. Multiple initializations are simply broken. Another CPU might have the device in use already after the first initialization and the second init could just render it unusable again. Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Signed-off-by: Ingo Molnar <mingo@elte.hu>		2008-09-05 11:11:52 +02:00
..
clockevents.c	clockevents: prevent clockevent event_handler ending up handler_noop	2008-09-05 11:11:51 +02: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
tick-broadcast.c	clockevents: prevent multiple init/shutdown	2008-09-05 11:11:52 +02:00
tick-common.c	clockevents: prevent clockevent event_handler ending up handler_noop	2008-09-05 11:11:51 +02:00
tick-internal.h
tick-oneshot.c	clockevents: enforce reprogram in oneshot setup	2008-09-05 11:11:52 +02:00
tick-sched.c	nohz: fix wrong event handler after online an offlined cpu	2008-08-21 09:54:06 +02:00
timekeeping.c
timer_list.c
timer_stats.c