diff options
author | Stephen Boyd <[email protected]> | 2013-04-17 10:26:06 -0700 |
---|---|---|
committer | Thomas Gleixner <[email protected]> | 2013-04-17 21:30:56 +0200 |
commit | c038c1c44179c80da6201f91ef354e48d5689617 (patch) | |
tree | a1ee34eadd567393cbdb6632ad7b8abb4a2fc4ea /drivers/scsi/mpt2sas/mpi/mpi2_raid.h | |
parent | b3956a896ea57f25cacd74708b8fab611543a81d (diff) |
clockevents: Switch into oneshot mode even if broadcast registered late
tick_oneshot_notify() is used to notify a particular CPU to try
to switch into oneshot mode after a oneshot capable tick device
is registered and tick_clock_notify() is used to notify all CPUs
to try to switch into oneshot mode after a high res clocksource
is registered. There is one caveat; if the tick devices suffer
from FEAT_C3_STOP we don't try to switch into oneshot mode unless
we have a oneshot capable broadcast device already registered.
If the broadcast device is registered after the tick devices that
have FEAT_C3_STOP we'll never try to switch into oneshot mode
again, causing us to be stuck in periodic mode forever. Avoid
this scenario by calling tick_clock_notify() after we register
the broadcast device so that we try to switch into oneshot mode
on all CPUs one more time.
[ tglx: Adopted to timers/core and added a comment ]
Signed-off-by: Stephen Boyd <[email protected]>
Link: http://lkml.kernel.org/r/[email protected]
Signed-off-by: Thomas Gleixner <[email protected]>
Diffstat (limited to 'drivers/scsi/mpt2sas/mpi/mpi2_raid.h')
0 files changed, 0 insertions, 0 deletions