Thomas Gleixner
c8a1d398de
clockevents: fix periodic broadcast for oneshot devices ...
The next_event member of the clock event device is used to keep track
of the next periodic event. For one shot only devices it is wrong to
clear the variable, as the next event will be based on it.
Pointed out by Ralf Baechle
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>
2007-10-12 23:04:06 +02:00
clockevents: Allow build w/o run-tine usage for migration purposes
2007-10-12 23:04:05 +02:00
clocksource: fix lock order in the resume path
2007-05-15 08:54:00 -07:00
[PATCH] fix jiffies clocksource inittime
2007-04-04 21:12:47 -07:00
clockevents: Allow build w/o run-tine usage for migration purposes
2007-10-12 23:04:05 +02:00
clockevents: Allow build w/o run-tine usage for migration purposes
2007-10-12 23:04:05 +02:00
Fix "no_sync_cmos_clock" logic inversion in kernel/time/ntp.c
2007-09-11 17:21:27 -07:00
clockevents: fix periodic broadcast for oneshot devices
2007-10-12 23:04:06 +02:00
clockevents: fix resume logic
2007-07-21 17:49:15 -07:00
highres/dyntick: prevent xtime lock contention
2007-05-08 11:15:10 -07:00
highres: improve debug output
2007-07-21 17:49:15 -07:00
clockevents: prevent stale tick update on offline cpu
2007-09-16 15:36:43 +02:00
timekeeping: Prevent time going backwards on resume
2007-09-16 15:36:43 +02:00
Fix leaks on /proc/{*/sched,sched_debug,timer_list,timer_stats}
2007-07-31 15:39:40 -07:00
Fix timer_stats printout of events/sec
2007-10-07 16:28:43 -07:00
c8a1d398de