Skip to contentSkip to conversation

watchdoug group ping

DISCUSSION fixed-term.Oleksij.Rempel 3 participants 3 messages Apr 20, 2016 – Apr 21, 2016 Watchdog device drivers

lore
Share & tools
lore
#0 lore raw

Hallo all,

my target is to provide pretimout support for devices which do not have this functionality.

Pre-requirement is this patchset (i contacted the author to rebase it against latest watchdog core branch):
https://www.mail-archive.com/[email protected]/msg02394.html

The idea is to use different watchdogs/timers or what ever as one group
- one virtual device.
One driver will be responsible for reseting the system, other for generating an interrupt on pre-timout.
It can be also useful for systems which require redundant watchdogs - two or more watchdog pinged over one /dev/watchdog

I assume i would need to create a master virtual watchdog driver to bypass/broadcast all pings to child devices.

Do you have some ideas or suggestions?

Signature · 4 lines
Best regards,
Oleksij Rempel
CM-AI/ECO3
Tel.: +49(5121)49-2962
maintainer
#1 lore raw
Quoted 16 lines · fixed-term.Oleksij.Rempel

Hallo all,

my target is to provide pretimout support for devices which do not have this functionality.

Pre-requirement is this patchset (i contacted the author to rebase it against latest watchdog core branch):
https://www.mail-archive.com/[email protected]/msg02394.html

The idea is to use different watchdogs/timers or what ever as one group
- one virtual device.
One driver will be responsible for reseting the system, other for generating an interrupt on pre-timout.
It can be also useful for systems which require redundant watchdogs - two or more watchdog pinged over one /dev/watchdog

Quoted 5 lines

I assume i would need to create a master virtual watchdog driver to bypass/broadcast all pings to child devices.

Do you have some ideas or suggestions?

Seems to add a lot of complexity. It might be much simpler to add support for a 'soft' pretimeout in such situations, ie a timer which fires at the correct interval and results in a reset. It might even be possible to use the new internal heartbeat function for this purpose.

Guenter

#2 lore raw

Am 21.04.2016 um 16:52 schrieb Guenter Roeck:

Quoted 20 lines · fixed-term.Oleksij.Rempel
Quoted 19 lines

Hallo all,

my target is to provide pretimout support for devices which do not have this functionality.

Pre-requirement is this patchset (i contacted the author to rebase it against latest watchdog core branch):
https://www.mail-archive.com/[email protected]/msg02394.html

The idea is to use different watchdogs/timers or what ever as one group
- one virtual device.
One driver will be responsible for reseting the system, other for generating an interrupt on pre-timout.
It can be also useful for systems which require redundant watchdogs - two or more watchdog pinged over one /dev/watchdog

I assume i would need to create a master virtual watchdog driver to bypass/broadcast all pings to child devices.

Quoted 6 lines
Quoted 2 lines

Do you have some ideas or suggestions?

Seems to add a lot of complexity. It might be much simpler to add support for a 'soft' pretimeout in such situations, ie a timer which fires at the correct interval and results in a reset. It might even be possible to use the new internal heartbeat function for this purpose.

yes, you have right. it is simple and cleaner generic way. i like it :)

Signature · 2 lines
Regards,
Oleksij