30 Dec, 2015
1 commit
-
A watchdog driver should not use watchdog subsystem internal flags.
Use a driver variable and flag instead to maintain the watchdog state
and to determine if a suspend operation is possible or not.Signed-off-by: Guenter Roeck
Signed-off-by: Wim Van Sebroeck
14 Oct, 2015
1 commit
-
Introduce /sys/debug/kernel/diag_stat with a statistic how many diagnose
calls have been done by each CPU in the system.Signed-off-by: Martin Schwidefsky
25 Mar, 2015
2 commits
-
This patch extends the diag288 watchdog driver to be able to deal with KVM
hypervisors. Only z/VM needs special handling, we can use the same interface
as on LPAR. Remove all pr_info output to avoid misconception. Because there
is no value in these messages and only the pr_err messages make sense.Signed-off-by: Xu Wang
Reviewed-by: David Hildenbrand
Acked-by: Heiko Carstens
Signed-off-by: Martin Schwidefsky -
There's no reason why we wouldn't want to be able to send a keep alive
message to /dev/watchdog (feed dog) for the s390 diag288 watchdog, so
let's enable the WDIOF_KEEPALIVEPING option.Signed-off-by: Xu Wang
Signed-off-by: Martin Schwidefsky
10 Jun, 2014
2 commits
-
Add the LPAR variant of the diag 288 watchdog to the driver.
The only available action on timeout for LPAR is a PSW restart.Signed-off-by: Philipp Hachtmann
Signed-off-by: Martin Schwidefsky -
Converted the vmwatchdog driver to use the kernel's watchdog API.
Signed-off-by: Philipp Hachtmann
Signed-off-by: Martin Schwidefsky
