From: Corey Minyard <minyard@acm.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
OpenIPMI Developers <openipmi-developer@lists.sourceforge.net>,
Wim Van Sebroeck <wim@iguana.be>
Subject: Re: [PATCH] watchdog: add pretimeout ioctl
Date: Tue, 27 Jun 2006 20:05:41 -0500 [thread overview]
Message-ID: <44A1D5E5.3020903@acm.org> (raw)
In-Reply-To: <1151434785.32186.56.camel@localhost.localdomain>
Alan Cox wrote:
> Ar Maw, 2006-06-27 am 13:22 -0500, ysgrifennodd minyard@acm.org:
>
>> Some watchdog timers support the concept of a "pretimeout" which
>> occurs some time before the real timeout. The pretimeout can
>> be delivered via an interrupt or NMI and can be used to panic
>> the system when it occurs (so you get useful information instead
>> of a blind reboot).
>>
>
> All watchdogs can do pre-timeouts in software so possibly this should
> use a software fallback as well if you want good coverage ?
>
I hadn't thought of that, but a software emulator could be used with
this interface, but it doesn't really help with hard lockups. This is
primarily intended to set up watchdogs that can delver an NMI,
since even if the machine is hard-locked the NMI will come through.
Of course, there's all kinds of problems with getting the NMI to a
useful handler, but that's another story.
-Corey
next prev parent reply other threads:[~2006-06-28 1:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 18:22 [PATCH] watchdog: add pretimeout ioctl minyard
2006-06-27 18:59 ` Alan Cox
2006-06-28 1:05 ` Corey Minyard [this message]
2006-06-28 10:27 ` Alan Cox
2006-06-28 0:29 ` Andrew Morton
2006-06-28 0:38 ` Corey Minyard
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=44A1D5E5.3020903@acm.org \
--to=minyard@acm.org \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=openipmi-developer@lists.sourceforge.net \
--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