From: Guenter Roeck <linux@roeck-us.net>
To: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>,
Wim Van Sebroeck <wim@iguana.be>
Cc: linux-watchdog@vger.kernel.org
Subject: Re: [PATCH 6/6] watchdog: pretimeout: add ping watchdog pretimeout governor
Date: Mon, 23 Nov 2015 22:36:23 -0800 [thread overview]
Message-ID: <56540567.1020803@roeck-us.net> (raw)
In-Reply-To: <1448089910-11453-7-git-send-email-vladimir_zapolskiy@mentor.com>
On 11/20/2015 11:11 PM, Vladimir Zapolskiy wrote:
> Ping watchdog pretimeout governor, on watchdog pretimeout event ping
> watchdog device. Use this watchdog pretimeout governor with caution,
> it may humiliate watchdog work, however it may be helpful in some
> particular situations, for instance if once started watchdog can not
> be stopped, but reboot caused by the watchdog is undesired.
>
> Signed-off-by: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
> ---
> drivers/watchdog/Kconfig | 16 +++++++++++++
> drivers/watchdog/Makefile | 1 +
> drivers/watchdog/pretimeout_ping.c | 48 ++++++++++++++++++++++++++++++++++++++
> 3 files changed, 65 insertions(+)
> create mode 100644 drivers/watchdog/pretimeout_ping.c
>
> diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig
> index 6c1f7e1..cb0885a 100644
> --- a/drivers/watchdog/Kconfig
> +++ b/drivers/watchdog/Kconfig
> @@ -1669,6 +1669,12 @@ config WATCHDOG_PRETIMEOUT_DEFAULT_GOV_DEVICE
> Use device specific watchdog pretimeout event handler
> by default.
>
> +config WATCHDOG_PRETIMEOUT_DEFAULT_GOV_PING
> + bool "ping"
> + select WATCHDOG_PRETIMEOUT_GOV_PING
> + help
> + Use ping watchdog pretimeout event handler by default.
> +
> endchoice
>
> config WATCHDOG_PRETIMEOUT_GOV_NOOP
> @@ -1698,6 +1704,16 @@ config WATCHDOG_PRETIMEOUT_GOV_DEVICE
> does nothing, if watchdog driver does not define a pretimeout
> callback.
>
> +config WATCHDOG_PRETIMEOUT_GOV_PING
> + tristate "Ping watchdog pretimeout governor"
> + help
> + Ping watchdog pretimeout governor, on watchdog pretimeout
> + event ping watchdog device. Use this watchdog pretimeout
> + governor with caution, it may humiliate watchdog work,
> + however it may be helpful in some particular situations,
> + for instance if once started watchdog can not be stopped,
> + but reboot caused by the watchdog is undesired.
> +
This one will be unnecessary once the pending infrastructure enhancements
are accepted. The watchdog core will then handle the ping.
I don't think this should be left to user space, as it _would_ defeat
the watchdog's purpose if the watchdog application fails to ping
the watchdog.
Thanks,
Guenter
> endif # WATCHDOG_PRETIMEOUT_GOV
>
> endif # WATCHDOG
> diff --git a/drivers/watchdog/Makefile b/drivers/watchdog/Makefile
> index 0717b64..bbf6af8 100644
> --- a/drivers/watchdog/Makefile
> +++ b/drivers/watchdog/Makefile
> @@ -12,6 +12,7 @@ obj-$(CONFIG_WATCHDOG_PRETIMEOUT_GOV_NOOP) += pretimeout_noop.o
> obj-$(CONFIG_WATCHDOG_PRETIMEOUT_GOV_PANIC) += pretimeout_panic.o
> obj-$(CONFIG_WATCHDOG_PRETIMEOUT_GOV_USERSPACE) += pretimeout_userspace.o
> obj-$(CONFIG_WATCHDOG_PRETIMEOUT_GOV_DEVICE) += pretimeout_device.o
> +obj-$(CONFIG_WATCHDOG_PRETIMEOUT_GOV_PING) += pretimeout_ping.o
>
> # Only one watchdog can succeed. We probe the ISA/PCI/USB based
> # watchdog-cards first, then the architecture specific watchdog
> diff --git a/drivers/watchdog/pretimeout_ping.c b/drivers/watchdog/pretimeout_ping.c
> new file mode 100644
> index 0000000..0d55205
> --- /dev/null
> +++ b/drivers/watchdog/pretimeout_ping.c
> @@ -0,0 +1,48 @@
> +/*
> + * Copyright (C) 2015 Mentor Graphics
> + *
> + * This program is free software; you can redistribute it and/or modify
> + * it under the terms of the GNU General Public License as published by
> + * the Free Software Foundation; either version 2 of the License, or
> + * (at your option) any later version.
> + *
> + */
> +
> +#include <linux/module.h>
> +#include <linux/watchdog.h>
> +
> +#include <watchdog_pretimeout.h>
> +
> +/**
> + * pretimeout_ping - Ping watchdog on pretimeout event
> + * @wdd - watchdog_device
> + *
> + */
> +static void pretimeout_ping(struct watchdog_device *wdd)
> +{
> + wdd->ops->ping(wdd);
> +}
> +
> +static struct watchdog_governor watchdog_gov_ping = {
> + .name = "ping",
> + .pretimeout = pretimeout_ping,
> +#ifdef CONFIG_WATCHDOG_PRETIMEOUT_DEFAULT_GOV_PING
> + .is_default = true,
> +#endif
> +};
> +
> +static int __init watchdog_gov_ping_register(void)
> +{
> + return watchdog_register_governor(&watchdog_gov_ping);
> +}
> +
> +static void __exit watchdog_gov_ping_unregister(void)
> +{
> + watchdog_unregister_governor(&watchdog_gov_ping);
> +}
> +module_init(watchdog_gov_ping_register);
> +module_exit(watchdog_gov_ping_unregister);
> +
> +MODULE_AUTHOR("Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>");
> +MODULE_DESCRIPTION("Ping watchdog pretimeout governor");
> +MODULE_LICENSE("GPL");
>
next prev parent reply other threads:[~2015-11-24 6:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-21 7:11 [PATCH 0/6] watchdog: add watchdog pretimeout framework Vladimir Zapolskiy
2015-11-21 7:11 ` [PATCH 1/6] " Vladimir Zapolskiy
2015-11-21 7:11 ` [PATCH 2/6] watchdog: pretimeout: add noop pretimeout governor Vladimir Zapolskiy
2015-11-21 7:11 ` [PATCH 3/6] watchdog: pretimeout: add panic " Vladimir Zapolskiy
2015-11-21 7:11 ` [PATCH 4/6] watchdog: pretimeout: add userspace notifier " Vladimir Zapolskiy
2015-11-21 7:11 ` [PATCH 5/6] watchdog: pretimeout: add device specific " Vladimir Zapolskiy
2015-11-24 6:37 ` Guenter Roeck
2015-11-24 13:25 ` Vladimir Zapolskiy
2015-11-24 13:50 ` Guenter Roeck
2015-11-21 7:11 ` [PATCH 6/6] watchdog: pretimeout: add ping watchdog " Vladimir Zapolskiy
2015-11-24 6:36 ` Guenter Roeck [this message]
2015-11-24 13:27 ` Vladimir Zapolskiy
2015-11-21 17:13 ` [PATCH 0/6] watchdog: add watchdog pretimeout framework Guenter Roeck
2015-11-23 0:38 ` Vladimir Zapolskiy
2015-11-24 6:47 ` Guenter Roeck
2015-11-24 13:25 ` Vladimir Zapolskiy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56540567.1020803@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-watchdog@vger.kernel.org \
--cc=vladimir_zapolskiy@mentor.com \
--cc=wim@iguana.be \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox