From: Mark Lord <kernel@teksavvy.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Arnd Bergmann <arnd@arndb.de>, Wim Van Sebroeck <wim@iguana.be>,
LKML <linux-kernel@vger.kernel.org>,
Linux Watchdog Mailing List <linux-watchdog@vger.kernel.org>
Subject: Re: [PATCH 7/10 v2] Generic Watchdog Timer Driver
Date: Sun, 19 Jun 2011 13:29:00 -0400 [thread overview]
Message-ID: <4DFE31DC.4080201@teksavvy.com> (raw)
In-Reply-To: <20110619151909.1403205d@lxorguk.ukuu.org.uk>
On 11-06-19 10:19 AM, Alan Cox wrote:
>>> Then you'd need an additional interface to specify which watchdog as soon
>>> as we support multiple watchdogs.
>>
>> You can always have multiple ways of setting nowayout -- hardware requirements,
>> global module option, local module option, and a new ioctl command -- but
>> what is being used is then the logical OR of all of them.
>
> An ioctl for it would make a lot of sense as watchdogs are often compiled
> in so currently there isn't a good way to runtime set this.
I wouldn't mind a kernel parameter to enable a hardware watchdog timer at boot.
Currently, there's a window at startup where the watchdog is not enabled,
and the system could lock up and die in there without it being triggered.
Cheers
next prev parent reply other threads:[~2011-06-19 17:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-18 17:25 [PATCH 7/10 v2] Generic Watchdog Timer Driver Wim Van Sebroeck
2011-06-18 19:07 ` Arnd Bergmann
2011-06-19 10:03 ` Alan Cox
2011-06-19 11:25 ` Arnd Bergmann
2011-06-19 14:19 ` Alan Cox
2011-06-19 17:29 ` Mark Lord [this message]
2011-06-22 20:13 ` Wim Van Sebroeck
2011-06-23 14:13 ` Mark Lord
2011-06-24 14:55 ` Arnd Bergmann
2011-06-24 19:17 ` Wim Van Sebroeck
2011-06-24 21:14 ` Arnd Bergmann
2011-06-22 19:56 ` Wim Van Sebroeck
2011-06-22 21:25 ` Alejandro Cabrera
2011-06-24 19:41 ` Wim Van Sebroeck
2011-06-24 20:10 ` Alejandro Cabrera
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=4DFE31DC.4080201@teksavvy.com \
--to=kernel@teksavvy.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.