diff options
| author | Thomas Gleixner <tglx@linutronix.de> | 2011-02-25 22:34:23 +0100 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@suse.de> | 2011-03-07 15:17:54 -0800 |
| commit | f3d155634f6fc7ee665731768ed6f85d04ef442c (patch) | |
| tree | c32122fe119117acbacfb9259624e3c22a8dcd54 /fs | |
| parent | 9efe56738fecd591b5bf366a325440f9b457ebd6 (diff) | |
| download | linux-stable-f3d155634f6fc7ee665731768ed6f85d04ef442c.tar.gz linux-stable-f3d155634f6fc7ee665731768ed6f85d04ef442c.tar.bz2 linux-stable-f3d155634f6fc7ee665731768ed6f85d04ef442c.zip | |
clockevents: Prevent oneshot mode when broadcast device is periodic
commit 3a142a0672b48a853f00af61f184c7341ac9c99d upstream.
When the per cpu timer is marked CLOCK_EVT_FEAT_C3STOP, then we only
can switch into oneshot mode, when the backup broadcast device
supports oneshot mode as well. Otherwise we would try to switch the
broadcast device into an unsupported mode unconditionally. This went
unnoticed so far as the current available broadcast devices support
oneshot mode. Seth unearthed this problem while debugging and working
around an hpet related BIOS wreckage.
Add the necessary check to tick_is_oneshot_available().
Reported-and-tested-by: Seth Forshee <seth.forshee@canonical.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
LKML-Reference: <alpine.LFD.2.00.1102252231200.2701@localhost6.localdomain6>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions