On Tue, Apr 09, 2013 at 09:07:58AM -0700, Guenter Roeck wrote: > > > Just look for the use of mod_timer in the watchdog directory. > > > > So looking at the mod_timer logic in various drivers, it seems regardless > > if the /dev/watchdog device is opened or not, if it is running, it will > > automagically kick the watchdog. > > > yes > > > This seems that we can avoid pulling in userspace pieces for this. Just > > load the driver and the hardware starts getting kicked. > > > Only if it is already running. Also, you don't want to rely on it, because you > lose protection against user space issues. IOW if something goes wrong with a runaway userspace app, the kernel blindly continues to kick the watchdog, which masks the problem, right? > > A second use is if the hw watchdog needs to be pinged more often than user > space can provide. Some of the HW watchdogs need a ping in one-second intervals > or even faster. > > > Is that true? And if so, do all drivers detect if the hardware is already > > running during their init? Or is it based on the first device open? > > > It is usually done in the probe function. Ok. Thanks for the understanding of how the softdog stuff works. However, we still have the problem that if the machine panics and we want to jump into the kdump kernel, we need to 'kick' the watchdog one more time. This provides us a sane sync point for determining how long we have to load the watchdog driver in the second kernel before the hardware reboots us. Otherwise the reboots are pretty random and nothing is guaranteed. Hence the need for some sort of patch resembling the one I posted. Soooooooo, any thoughts about that patch and what changes I should make? :-) Cheers, Don
