Default behavior of watchdog drivers
Wim Van Sebroeck
maintainerhi Jean, Guenter,
Quoted 27 lines
Hi Jean,
Quoted 10 lines · Jean Delvare
Hello,
It seems that various watchdog drivers behave differently if the watchdog timer is already enabled when the driver is loaded:
*
iTCO_wdtwill disable the timer. I think this is what most drivers do, but not all.
*w83627hf_wdtwill let the timer run, unless option early_disable=1 is passed.Quoted 8 lines
These are the 2 which bother me the most because they are among the most popular watchdog drivers on x86 systems. Having a different behavior depending on which driver is used is quite confusing.
Can we please settle on a default behavior (either all drivers reset the timer a load time, or none do it) and have all watchdog drivers stick to that?
Since
ee142889e32fwatchdog: IntroduceWDOG_HW_RUNNINGflag664a39236e71watchdog: Introduce hardware maximum heartbeat in watchdog core
Quoted 6 lines
the default behavior _should_ be that the timer is kept running but the core is informed that it is running. Of course, that doesn't mean that (legacy) drivers actually do that.
Please note that some watchdog drivers can not be stopped, so a common mechanism to stop watchdogs during probe is technically impossible.
Originally the default behaviour was to stop the watchdog if it was running and restart it when /dev/watchdog was opened.
However some watchdog devices can't be stopped once running and the starting of it or not is done on "BIOS" level. So there we said that if the watchdog is allready running and it can't be stopped that the core should keep the watchdog running as long as the device is not "opened".
So the correct behaviour is that we should not have the watchdog device active if the device is not being used, but when the device can't be stopped then we need to keep the watchdog running and do the keepalive ping ourselves. It makes no sense to start the watchdog and ping it while itis not in use and can be stopped.
So looking at Jean's comment I think we need to review how w83627hf_wdt does the logic.
Quoted 7 lines
Quoted 7 lines
If an option to get the opposite behavior is deemed useful, can we settle on a standard name for it? Or even implement it at the
watchdog_corelevel, so that each driver doesn't need to implement it separately?While looking into this, I found a few other strange module parameters:
Quoted 19 lines
Quoted 2 lines
*
f71808e_wdthas "start_withtimeout", which starts the timer even if nobody opens the watchdog device node. Giel, do we really need this?We had requests for a common mechanism to do that, ie some kind of boot timeout. Idea would be to reboot the system if the watchdog device has not been opened after a set period of time. Maybe that is the idea here.
Guenter
Quoted 9 lines
* octeon-wdt has "disable", which completely disables the watchdog function. This "feature" was sneaked in via commit
381cec022e46("watchdog: octeon-wdt: File cleaning.") which was supposed to be a cleanup-only patch, without any explanation nor even mention. I can't see how such an option can be useful. If you don't need the driver, just don't load it. Steven, can you explain?Thanks,
Kind regards,
Wim.
Guenter Roeck
maintainerQuoted 36 lines · Wim Van Sebroeck
hi Jean, Guenter,
Quoted 27 lines
Hi Jean,
Quoted 10 lines · Jean Delvare
Hello,
It seems that various watchdog drivers behave differently if the watchdog timer is already enabled when the driver is loaded:
*
iTCO_wdtwill disable the timer. I think this is what most drivers do, but not all.
*w83627hf_wdtwill let the timer run, unless option early_disable=1 is passed.Quoted 8 lines
These are the 2 which bother me the most because they are among the most popular watchdog drivers on x86 systems. Having a different behavior depending on which driver is used is quite confusing.
Can we please settle on a default behavior (either all drivers reset the timer a load time, or none do it) and have all watchdog drivers stick to that?
Since
ee142889e32fwatchdog: IntroduceWDOG_HW_RUNNINGflag664a39236e71watchdog: Introduce hardware maximum heartbeat in watchdog coreQuoted 6 lines
the default behavior _should_ be that the timer is kept running but the core is informed that it is running. Of course, that doesn't mean that (legacy) drivers actually do that.
Please note that some watchdog drivers can not be stopped, so a common mechanism to stop watchdogs during probe is technically impossible.
Quoted 7 lines
Originally the default behaviour was to stop the watchdog if it was running and restart it when
/dev/watchdogwas opened.
However some watchdog devices can't be stopped once running and the starting of it or not is done on "BIOS" level. So there we said that if the watchdog is allready running and it can't be stopped that the core should keep the watchdog running as long as the device is not "opened".So the correct behaviour is that we should not have the watchdog device active if the device is not being used, but when the device can't be stopped then we need to keep the watchdog running and do the keepalive ping ourselves. It makes no sense to start the watchdog and ping it while itis not in use and can be stopped.
So looking at Jean's comment I think we need to review how
w83627hf_wdtdoes the logic.
I have seen requests that evrn watchdogs which can be stopped should be kept running to ensure that the system is always protected. Given that, I would hesitate to take that functionality away from the w83627hf_wdt driver.
Guenter
Quoted 31 lines
Quoted 7 lines
Quoted 7 lines
If an option to get the opposite behavior is deemed useful, can we settle on a standard name for it? Or even implement it at the
watchdog_corelevel, so that each driver doesn't need to implement it separately?While looking into this, I found a few other strange module parameters:
Quoted 19 lines
Quoted 2 lines
*
f71808e_wdthas "start_withtimeout", which starts the timer even if nobody opens the watchdog device node. Giel, do we really need this?We had requests for a common mechanism to do that, ie some kind of boot timeout. Idea would be to reboot the system if the watchdog device has not been opened after a set period of time. Maybe that is the idea here.
Guenter
Quoted 9 lines
* octeon-wdt has "disable", which completely disables the watchdog function. This "feature" was sneaked in via commit
381cec022e46("watchdog: octeon-wdt: File cleaning.") which was supposed to be a cleanup-only patch, without any explanation nor even mention. I can't see how such an option can be useful. If you don't need the driver, just don't load it. Steven, can you explain?Thanks,
Kind regards,
Wim.
Wim Van Sebroeck
maintainerHi Guenter,
Quoted 42 lines · Wim Van Sebroeck
Quoted 41 lines
hi Jean, Guenter,
Quoted 27 lines
Hi Jean,
Quoted 10 lines · Jean Delvare
Hello,
It seems that various watchdog drivers behave differently if the watchdog timer is already enabled when the driver is loaded:
*
iTCO_wdtwill disable the timer. I think this is what most drivers do, but not all.
*w83627hf_wdtwill let the timer run, unless option early_disable=1 is passed.Quoted 8 lines
These are the 2 which bother me the most because they are among the most popular watchdog drivers on x86 systems. Having a different behavior depending on which driver is used is quite confusing.
Can we please settle on a default behavior (either all drivers reset the timer a load time, or none do it) and have all watchdog drivers stick to that?
Since
ee142889e32fwatchdog: IntroduceWDOG_HW_RUNNINGflag664a39236e71watchdog: Introduce hardware maximum heartbeat in watchdog coreQuoted 6 lines
the default behavior _should_ be that the timer is kept running but the core is informed that it is running. Of course, that doesn't mean that (legacy) drivers actually do that.
Please note that some watchdog drivers can not be stopped, so a common mechanism to stop watchdogs during probe is technically impossible.
Originally the default behaviour was to stop the watchdog if it was running and restart it when
/dev/watchdogwas opened.
However some watchdog devices can't be stopped once running and the starting of it or not is done on "BIOS" level. So there we said that if the watchdog is allready running and it can't be stopped that the core should keep the watchdog running as long as the device is not "opened".So the correct behaviour is that we should not have the watchdog device active if the device is not being used, but when the device can't be stopped then we need to keep the watchdog running and do the keepalive ping ourselves. It makes no sense to start the watchdog and ping it while itis not in use and can be stopped.
Quoted 7 lines
Quoted 2 lines
So looking at Jean's comment I think we need to review how
w83627hf_wdtdoes the logic.I have seen requests that evrn watchdogs which can be stopped should be kept running to ensure that the system is always protected. Given that, I would hesitate to take that functionality away from the
w83627hf_wdtdriver.
That's not according to the specs that stipulate that it is userspace that should control that. And if it's not default behaviour then you could fix it by a module_param that enables that if you set it to do that.
Quoted 34 lines
Guenter
Quoted 31 lines
Quoted 7 lines
Quoted 7 lines
If an option to get the opposite behavior is deemed useful, can we settle on a standard name for it? Or even implement it at the
watchdog_corelevel, so that each driver doesn't need to implement it separately?While looking into this, I found a few other strange module parameters:
Quoted 19 lines
Quoted 2 lines
*
f71808e_wdthas "start_withtimeout", which starts the timer even if nobody opens the watchdog device node. Giel, do we really need this?We had requests for a common mechanism to do that, ie some kind of boot timeout. Idea would be to reboot the system if the watchdog device has not been opened after a set period of time. Maybe that is the idea here.
Guenter
Quoted 9 lines
* octeon-wdt has "disable", which completely disables the watchdog function. This "feature" was sneaked in via commit
381cec022e46("watchdog: octeon-wdt: File cleaning.") which was supposed to be a cleanup-only patch, without any explanation nor even mention. I can't see how such an option can be useful. If you don't need the driver, just don't load it. Steven, can you explain?Thanks,
Kind regards,
Wim.
Kind regards,
Wim.
Guenter Roeck
maintainerHi Wim,
Quoted 47 lines · Wim Van Sebroeck
Hi Guenter,
Quoted 45 lines · Wim Van Sebroeck
Quoted 43 lines
hi Jean, Guenter,
Quoted 27 lines
Hi Jean,
Quoted 10 lines · Jean Delvare
Hello,
It seems that various watchdog drivers behave differently if the watchdog timer is already enabled when the driver is loaded:
*
iTCO_wdtwill disable the timer. I think this is what most drivers do, but not all.
*w83627hf_wdtwill let the timer run, unless option early_disable=1 is passed.Quoted 8 lines
These are the 2 which bother me the most because they are among the most popular watchdog drivers on x86 systems. Having a different behavior depending on which driver is used is quite confusing.
Can we please settle on a default behavior (either all drivers reset the timer a load time, or none do it) and have all watchdog drivers stick to that?
Since
ee142889e32fwatchdog: IntroduceWDOG_HW_RUNNINGflag664a39236e71watchdog: Introduce hardware maximum heartbeat in watchdog coreQuoted 6 lines
the default behavior _should_ be that the timer is kept running but the core is informed that it is running. Of course, that doesn't mean that (legacy) drivers actually do that.
Please note that some watchdog drivers can not be stopped, so a common mechanism to stop watchdogs during probe is technically impossible.
Originally the default behaviour was to stop the watchdog if it was running and restart it when
/dev/watchdogwas opened.
However some watchdog devices can't be stopped once running and the starting of it or not is done on "BIOS" level. So there we said that if the watchdog is allready running and it can't be stopped that the core should keep the watchdog running as long as the device is not "opened".So the correct behaviour is that we should not have the watchdog device active if the device is not being used, but when the device can't be stopped then we need to keep the watchdog running and do the keepalive ping ourselves. It makes no sense to start the watchdog and ping it while itis not in use and can be stopped.
So looking at Jean's comment I think we need to review how
w83627hf_wdtdoes the logic.
Quoted 8 lines
Quoted 4 lines
I have seen requests that evrn watchdogs which can be stopped should be kept running to ensure that the system is always protected. Given that, I would hesitate to take that functionality away from the
w83627hf_wdtdriver.That's not according to the specs that stipulate that it is userspace that should control that. And if it's not default behaviour then you could fix it by a
module_paramthat enables that if you set it to do that.
It is difficult for userspace to control behavior that applies prior to userspace running.
There have been some arguments back and forth discussing how and when to enable the watchdog prior to userspace opening it (and what the initial timeout should be). Maybe it is time to revisit that and find a consistent solution.
Thanks,
Guenter
Quoted 39 lines
Quoted 34 lines
Guenter
Quoted 31 lines
Quoted 7 lines
Quoted 7 lines
If an option to get the opposite behavior is deemed useful, can we settle on a standard name for it? Or even implement it at the
watchdog_corelevel, so that each driver doesn't need to implement it separately?While looking into this, I found a few other strange module parameters:
Quoted 19 lines
Quoted 2 lines
*
f71808e_wdthas "start_withtimeout", which starts the timer even if nobody opens the watchdog device node. Giel, do we really need this?We had requests for a common mechanism to do that, ie some kind of boot timeout. Idea would be to reboot the system if the watchdog device has not been opened after a set period of time. Maybe that is the idea here.
Guenter
Quoted 9 lines
* octeon-wdt has "disable", which completely disables the watchdog function. This "feature" was sneaked in via commit
381cec022e46("watchdog: octeon-wdt: File cleaning.") which was supposed to be a cleanup-only patch, without any explanation nor even mention. I can't see how such an option can be useful. If you don't need the driver, just don't load it. Steven, can you explain?Thanks,
Kind regards,
Wim.Kind regards,
Wim.