On 05/24/2015 03:15 AM, Fu Wei wrote:
Hi Guenter,
On 24 May 2015 at 04:01, Guenter Roeck <linux@xxxxxxxxxxxx> wrote:
On 05/23/2015 12:40 PM, Timur Tabi wrote:
[ ... ]
I use emergency_restart(), because the watchdog-api.txt documentation says
this:
"If userspace fails (RAM error, kernel bug, whatever), the
notifications cease to occur, and the hardware watchdog will reset the
system (causing a reboot) after the timeout occurs."
Maybe I'm reading this too literally, but to me this means that when the
timeout expires, the system has to reset immediately.
However, maybe panic() is better, since it can do the same thing and more.
I have a specific requirement at work to have watchdog expiration
(not this watchdog, this is different HW) result in a panic, specifically
to enable crashdump support and thus post-mortem analysis.
I had not thought about this use case myself, and I had always wondered
why watchdog driver implementers would choose to call panic() after an
interrupt or NMI. But we live and learn, so now I finally understand.
In the pretimeout/timeout world, the pretimeout would (typically)
result in a panic, and the timeout would result in a reset. So one
would set the timer register to 10s for 10s pretimeout and 20s timeout.
However, the pretimeout concept assumes that there are two timers
which can be set independently. As you had pointed out earlier,
and as the specification seems to confirm, that is not the case here.
Sorry, in Documentation/watchdog/watchdog-api.txt, I can not get the
info about " the pretimeout concept assumes that there are two timers
which can be set independently."
Could you kindly point out where is the assumption.
I thinks in kernel documentation, that meams "one watchdog has two
timeout stages", maybe I miss something. Could you help me out?
My apologies. Terminology problem; see below.
Note that the pretimeout, as documented, is a difference to the real
timeout, not an absolute time (which I had not realized before).
"Note that the pretimeout is the number of seconds before the time
when the timeout will go off. It is not the number of seconds until
the pretimeout. So, for instance, if you set the timeout to 60 seconds
and the pretimeout to 10 seconds, the pretimeout will go off in 50
seconds. Setting a pretimeout to zero disables it."
As such, I don't really understand why and how the pretimeout / timeout
concept would add any value here and not just make things more
complicated than necessary. Maybe I am just missing something.
If pretimeout concept assumes that there are two timers, I
misunderstand the "pretimeout", then I will delete the pretimeout
immediately.
I think I used the wrong term. I should have said something like
"two distinct timeout values".
Guenter
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
