From: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
To: "Jerry.Hoemann@hpe.com" <Jerry.Hoemann@hpe.com>
Cc: "linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
Guenter Roeck <linux@roeck-us.net>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Jonathan Corbet <corbet@lwn.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
Esben Haabendal <esben@haabendal.dk>,
"martin@hundeboll.net" <martin@hundeboll.net>,
Rasmus Villemoes <Rasmus.Villemoes@prevas.se>
Subject: Re: [PATCH v9 0/3] watchdog: allow setting deadline for opening /dev/watchdogN
Date: Wed, 1 May 2019 06:32:02 +0000 [thread overview]
Message-ID: <31d75b51-6cd6-9029-40a5-fec631e110bf@prevas.dk> (raw)
In-Reply-To: <20190501000511.GA25050@anatevka>
On 01/05/2019 02.05, Jerry Hoemann wrote:
> On Mon, Jan 21, 2019 at 08:45:38PM +0000, Rasmus Villemoes wrote:
>>
>> These patches allow one to set a maximum time for which the kernel
>> will feed the watchdog,
>
> Rasmus,
>
> Sorry if I missed it, but are you still looking into adding
> this feature?
I am, and still intend to get around to it when I get some idle cycles.
I was thinking it might also be useful with
> kdump when a watchdog was running in the first kernel.
>
> After a panic if kdump is configured, the system will boot the
> crash kernel. If a watchdog was running in the first kernel
> it would still running in the crash kernel environment.
>
> Some of the drivers on HPE systems take a non-trivial amount of time
> to reset during the crash kernel boot, so it would be good to have
> the core pet the watchdog until user space is ready. But as the
> crash kernel environment has its issues, we really don't want
> the core to ping the watchdog indefinitely.
Thanks, it's great to hear that others would also be interested in this.
This will move it up a few places on my todo list. I'll try to remember
to add you to the cc list.
Thanks,
Rasmus
prev parent reply other threads:[~2019-05-01 6:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 12:14 [PATCH v8 0/3] watchdog: allow setting deadline for opening /dev/watchdogN Rasmus Villemoes
2019-01-16 12:14 ` [PATCH v8 1/3] watchdog: introduce watchdog.open_timeout commandline parameter Rasmus Villemoes
2019-01-17 21:24 ` Guenter Roeck
2019-01-16 12:14 ` [PATCH v8 2/3] watchdog: introduce CONFIG_WATCHDOG_OPEN_TIMEOUT Rasmus Villemoes
2019-01-16 12:14 ` [PATCH v8 3/3] watchdog: make the device time out at open_deadline when open_timeout is used Rasmus Villemoes
2019-01-16 14:45 ` [PATCH v8 0/3] watchdog: allow setting deadline for opening /dev/watchdogN Esben Haabendal
2019-01-21 20:45 ` [PATCH v9 " Rasmus Villemoes
2019-01-21 20:45 ` [PATCH v9 1/3] watchdog: introduce watchdog.open_timeout commandline parameter Rasmus Villemoes
2019-01-22 17:29 ` Guenter Roeck
2019-01-29 20:35 ` Rasmus Villemoes
2019-01-30 7:40 ` Rasmus Villemoes
2019-01-21 20:45 ` [PATCH v9 2/3] watchdog: introduce CONFIG_WATCHDOG_OPEN_TIMEOUT Rasmus Villemoes
2019-01-21 20:45 ` [PATCH v9 3/3] watchdog: make the device time out at open_deadline when open_timeout is used Rasmus Villemoes
2019-05-01 0:05 ` [PATCH v9 0/3] watchdog: allow setting deadline for opening /dev/watchdogN Jerry Hoemann
2019-05-01 6:32 ` Rasmus Villemoes [this message]
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=31d75b51-6cd6-9029-40a5-fec631e110bf@prevas.dk \
--to=rasmus.villemoes@prevas.dk \
--cc=Jerry.Hoemann@hpe.com \
--cc=Rasmus.Villemoes@prevas.se \
--cc=corbet@lwn.net \
--cc=esben@haabendal.dk \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=martin@hundeboll.net \
--cc=wim@linux-watchdog.org \
/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;
as well as URLs for NNTP newsgroup(s).