| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20071029194503.GB27646@csclub.uwaterloo.ca> Date: Mon, 29 Oct 2007 15:45:03 -0400 From: lsorense@...lub.uwaterloo.ca (Lennart Sorensen) To: Stefan Roese <stefan.roese@...il.com> Cc: linux-kernel@...r.kernel.org Subject: Re: Bootup support for watchdog with short timeout (touch_nmi_watchdog()?) On Mon, Oct 29, 2007 at 03:22:27PM +0100, Stefan Roese wrote: > I'm trying to implement support for a board specific watchdog on a PPC440EPx > board with a very short timeout. In this case, the watchdog has to > be "kicked" at least every 100ms, even while booting and the real watchdog > driver not running yet. While looking for trigger places in the kernel > source, I noticed the already existing "touch_nmi_watchdog()" function, which > seems to be doing what I need. Even if the name not exactly matches my > hardware setup. > > My question now is, is it recommended to use this > touch_nmi_watchdog() "infrastructure" for my PPC custom specific watchdog > during bootup? And if yes, should it perhaps be renamed to a more generic > name, like "touch_watchdog"? > > Please advise. Thanks. No idea really. Who would design a watchdog with such a short trigger time? That doesn't seem to be useful in any way. -- Len Sorensen - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists