From: Guenter Roeck <linux@roeck-us.net>
To: Pratyush Anand <panand@redhat.com>, linux-watchdog@vger.kernel.org
Cc: Dave Young <dyoung@redhat.com>, Don Zickus <dzickus@redhat.com>
Subject: Re: Query: Best way to know if a watchdog is active (kicked)
Date: Mon, 17 Aug 2015 22:39:48 -0700 [thread overview]
Message-ID: <55D2C524.1060903@roeck-us.net> (raw)
In-Reply-To: <20150818051532.GC27149@dhcppc13.redhat.com>
On 08/17/2015 10:15 PM, Pratyush Anand wrote:
> Hi,
>
> I am looking for the best way to know if a watchdog has been kicked and active.
>
> I can see a way is to read timeout(WDIOC_GETTIMEOUT) and timeleft(
> WDIOC_GETTIMELEFT). If they do not match, it means that wdt is active.
>
> But what if we tried to read timeleft just in time when watchdog daemon/or some
> other application had kicked it. May be we read timeleft twice at the interval
> of 1 sec.
>
> Please let me know if there is any other alternative which could be a better way
> to know if watchdog is active? Or may be it would be good to implement an ioctl
> WDIOC_ACTIVE?
>
Normally the watchdog is active if the watchdog device is open, unless the
application controlling it explicitly disabled it with WDIOC_SETOPTIONS.
Therefore, the controlling application should always know the status.
A different application can not open the watchdog device, so it won't be
able to get its status using an ioctl anyway.
Why is that insufficient ?
Guenter
next prev parent reply other threads:[~2015-08-18 5:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 5:15 Query: Best way to know if a watchdog is active (kicked) Pratyush Anand
2015-08-18 5:39 ` Guenter Roeck [this message]
2015-08-18 6:57 ` Pratyush Anand
2015-08-18 9:13 ` Dave Young
2015-08-18 9:52 ` Pratyush Anand
2015-08-18 12:50 ` Guenter Roeck
2015-08-18 13:08 ` Pratyush Anand
2015-08-18 14:23 ` Guenter Roeck
2015-08-21 8:52 ` Pratyush Anand
2015-08-21 15:19 ` Guenter Roeck
2015-08-21 17:05 ` Pratyush Anand
2015-08-21 17:13 ` Guenter Roeck
2015-08-21 17:19 ` Pratyush Anand
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=55D2C524.1060903@roeck-us.net \
--to=linux@roeck-us.net \
--cc=dyoung@redhat.com \
--cc=dzickus@redhat.com \
--cc=linux-watchdog@vger.kernel.org \
--cc=panand@redhat.com \
/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