48e8ac2979
With recent changes it is possible for the timer handler to detect an idle interface and not start the timer, but the thread to start an operation at the same time. The thread will not start the timer in that instance, resulting in the timer not running. Instead, move all timer operations under the lock and start the timer in the thread if it detect non-idle and the timer is not already running. Moving under locks allows the last timeout to be set in both the thread and the timer. 'Timer is not running' means that the timer is not pending and smi_timeout() is not running. So we need a flag to detect this correctly. Also fix a few other timeout bugs: setting the last timeout when the interrupt has to be disabled and the timer started, and setting the last timeout in check_start_timer_thread possibly racing with the timer Signed-off-by: Corey Minyard <cminyard@mvista.com> Signed-off-by: Bodo Stroesser <bstroesser@ts.fujitsu.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> |
||
|---|---|---|
| .. | ||
| ipmi_bt_sm.c | ||
| ipmi_devintf.c | ||
| ipmi_kcs_sm.c | ||
| ipmi_msghandler.c | ||
| ipmi_poweroff.c | ||
| ipmi_si_intf.c | ||
| ipmi_si_sm.h | ||
| ipmi_smic_sm.c | ||
| ipmi_watchdog.c | ||
| Kconfig | ||
| Makefile | ||