xen_wdt_release() shouldn't clear is_active even when the watchdog
didn't get stopped (which by itself shouldn't happen, but let's return
a proper error in this case rather than adding a BUG() upon hypercall
failure).
Signed-off-by: NJan Beulich <jbeulich@suse.com>
Signed-off-by: NWim Van Sebroeck <wim@iguana.be>

This was found to be a problem particularly after guest migration.
Signed-off-by: NJan Beulich <jbeulich@suse.com>
Reported-by: NWouter de Geus <benv-xensource.com@junerules.com>
Reported-by: NIan Campbell <Ian.Campbell@citrix.com>
Tested-by: NWouter de Geus <benv-xensource.com@junerules.com>
Signed-off-by: NWim Van Sebroeck <wim@iguana.be>

Use the current logging styles.

Make sure all output has a prefix.
Add missing newlines.
Remove now unnecessary PFX, NAME, and miscellaneous other #defines.
Coalesce formats.
Signed-off-by: NJoe Perches <joe@perches.com>
Signed-off-by: NWim Van Sebroeck <wim@iguana.be>

While the hypervisor change adding SCHEDOP_watchdog support included a
daemon to make use of the new functionality, having a kernel driver
for /dev/watchdog so that user space code doesn't need to distinguish
non-Xen and Xen seems to be preferable.
Signed-off-by: NJan Beulich <jbeulich@novell.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>
Signed-off-by: NWim Van Sebroeck <wim@iguana.be>