On 10/28/2011 11:48 AM, Don Zickus wrote:
On Fri, Oct 28, 2011 at 11:46:30AM -0400, Alejandro Cabrera wrote:
Hi
I dont know kjump :), but seeing it's description I think that you
could use a temporal thread executed in the context of kdump that
ping the watchdog at certain intervals like watchdogd does at
user-space.
Sure. Add something like watchdogd isn't difficult. My problem is
getting enough time to boot the second kernel to run that daemon.
Depending on when the watchdog was last kicked, the machine may reboot
while trying to initialize the cpu in the second kernel. :-(
You can create the daemon in kdump before the second kernel boots and
manage that daemon as a kdump thread.
While the second kernel is booting kdump will act as the owner of the
watchdog device and when the second kernel is stable, kdump passes the
control of it to the watchdog kernel device driver.
If is not problem, that two threads (kdump daemon and second kernel
watchdog driver) access to the device simultaneously and without sync (I
think IMMO that for pinging the watchdog it is not a issue) you can
bypass the part that second kernel wdt drivers waits a notification from
kdump to start working with the watchdog device.
Regards
Alejandro
Participe en Universidad 2012, del 13 al 17 de febrero de 2012.
Habana, Cuba: http://www.congresouniversidad.cu
Consulte la enciclopedia colaborativa cubana. http://www.ecured.cu
Participe en el Segundo Congreso Medio Ambiente Construido y
Desarrollo Sustentable (MACDES 2011) del 6 al 9 de diciembre de 2011,
Hotel Nacional, Habana, Cuba: http://macdes.cujae.edu.cu
--
To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
