| commit | fba9110fee9fc438cfd9b6c1091bfda8710875b5 | |
| author | Bo Tu <tubo@linux.vnet.ibm.com> | |
| Tue, 19 Jan 2016 07:45:19 +0000 (19 08:45 +0100) | ||
| committer | Cornelia Huck <cornelia.huck@de.ibm.com> | |
| Wed, 27 Jan 2016 14:34:47 +0000 (27 15:34 +0100) | ||
| tree | 1ba3abdeaf66519aac9257c0c9193cec0863017e | treesnapshot (tar.gz zip) |
| parent | 0d035b6c5e8292b02045c372eea248298c0f2f62 | commitdiff |
watchdog/diag288: don't reset for action=none|debug|pause
If the watchdog expires and the guest is not notified (NONE, DEBUG, PAUSE),
we must not reset the watchdog device, otherwise watchdog_ping() and
watchdog_stop() will fail when triggered by the guest. This reset behavior
matches to the z/VM behavior when a custom command is to be executed
on expiry.
Reviewed-by: David Hildenbrand <dahi@linux.vnet.ibm.com>
Signed-off-by: Bo Tu <tubo@linux.vnet.ibm.com>
Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
If the watchdog expires and the guest is not notified (NONE, DEBUG, PAUSE),
we must not reset the watchdog device, otherwise watchdog_ping() and
watchdog_stop() will fail when triggered by the guest. This reset behavior
matches to the z/VM behavior when a custom command is to be executed
on expiry.
Reviewed-by: David Hildenbrand <dahi@linux.vnet.ibm.com>
Signed-off-by: Bo Tu <tubo@linux.vnet.ibm.com>
Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
| hw/watchdog/wdt_diag288.c | diffblobblamehistory |