remarkable-linux/kernel/time
Thomas Gleixner 302745699c clockevents: check broadcast device not tick device
Impact: Possible hang on CPU online observed on AMD C1E machines.

The broadcast setup code looks at the mode of the tick device to
determine whether it needs to be shut down or setup. This is wrong
when the broadcast mode is set to one shot already. This can happen
when a CPU is brought online as it goes through the periodic setup
first.

The problem went unnoticed as sane systems do not call into that code
before the switch to one shot for the clock event device happens.
The AMD C1E idle routine switches over immediately and thereby shuts
down the just setup device before the first interrupt happens.

Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
2008-09-23 11:38:53 +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 device not tick device 2008-09-23 11:38:53 +02:00
tick-common.c clockevents: prevent cpu online to interfere with nohz 2008-09-23 11:38:52 +02:00
tick-internal.h clockevents: prevent cpu online to interfere with nohz 2008-09-23 11:38:52 +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 clockevents: prevent stale tick_next_period for onlining CPUs 2008-09-23 11:38:53 +02:00
timekeeping.c ntp: handle leap second via timer 2008-05-01 08:03:59 -07:00
timer_list.c kernel: use non-racy method for proc entries creation 2008-04-29 08:06:22 -07:00
timer_stats.c kernel: use non-racy method for proc entries creation 2008-04-29 08:06:22 -07:00