From: Corey Minyard <minyard@acm.org>
To: Rudolf Marek <r.marek@sh.cvut.cz>
Cc: wim@iguana.be, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Watchdog device class
Date: Tue, 18 Apr 2006 18:07:20 -0500 [thread overview]
Message-ID: <44457128.2010708@acm.org> (raw)
In-Reply-To: <4443EED9.30603@sh.cvut.cz>
Rudolf Marek wrote:
>
> The char device of watchdog class is compatible with existing watchdog
> API,
> so no need to change the user applications. There is just one exception
> and this is temperature handling. I belive it should be implemented not
> via IOCTL but using the HWMON class. (100% compatibility can be restored
> with the ioctl class op)
>
> I have defined this class ops so far:
>
> struct watchdog_class_ops {
> int (*enable)(struct device *);
> int (*disable)(struct device *);
> int (*ping)(struct device *);
> int (*set_timeout)(struct device *, int sec);
> int (*notify_reboot)(struct notifier_block *this, unsigned long code,
> void *unused);
> };
Some watchdog devices have the ability to say "I'm about to reboot you,
do you want to do something about it?". The IPMI watchdog calls this a
pretimeout, but I have seen this concept on at least two other watchdog
devices. This can be delivered via an NMI or SMI and can be used to
inform the OS ahead of time that it's going to reboot the system. This
is useful because you can panic, do a coredump, or perform other useful
operations instead of just rebooting.
Do you think this interface belongs in the structure?
-Corey
next prev parent reply other threads:[~2006-04-18 23:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-17 19:39 [RFC] Watchdog device class Rudolf Marek
2006-04-17 21:31 ` Alan Cox
2006-04-18 18:35 ` Rudolf Marek
2006-04-18 20:16 ` Alan Cox
2006-04-18 0:54 ` Arnd Bergmann
2006-04-18 19:32 ` Rudolf Marek
2006-04-18 22:24 ` Mark Rustad
2006-04-18 19:57 ` Wim Van Sebroeck
2006-04-18 20:59 ` Rudolf Marek
2006-04-19 21:02 ` Wim Van Sebroeck
2006-04-19 21:24 ` Rudolf Marek
2006-08-15 17:13 ` Wim Van Sebroeck
2006-09-14 12:19 ` Rudolf Marek
2006-04-18 23:07 ` Corey Minyard [this message]
2006-04-19 21:04 ` Wim Van Sebroeck
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=44457128.2010708@acm.org \
--to=minyard@acm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=r.marek@sh.cvut.cz \
--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