Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751920AbbHEHgO (ORCPT ); Wed, 5 Aug 2015 03:36:14 -0400 Received: from metis.ext.pengutronix.de ([92.198.50.35]:35344 "EHLO metis.ext.pengutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751239AbbHEHgM (ORCPT ); Wed, 5 Aug 2015 03:36:12 -0400 Date: Wed, 5 Aug 2015 09:36:05 +0200 From: Uwe =?iso-8859-1?Q?Kleine-K=F6nig?= To: =?iso-8859-1?Q?P=E1draig?= Brady Cc: Guenter Roeck , linux-watchdog@vger.kernel.org, Wim Van Sebroeck , linux-kernel@vger.kernel.org, Timo Kokkonen , linux-doc@vger.kernel.org, Jonathan Corbet Subject: Re: [PATCH 0/8] watchdog: Add support for keepalives triggered by infrastructure Message-ID: <20150805073605.GW9999@pengutronix.de> References: <1438654414-29259-1-git-send-email-linux@roeck-us.net> <55C14E2B.1080904@draigBrady.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <55C14E2B.1080904@draigBrady.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: 2001:67c:670:100:1d::c0 X-SA-Exim-Mail-From: ukl@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: linux-kernel@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1938 Lines: 40 Hello P?draig, On Wed, Aug 05, 2015 at 12:43:39AM +0100, P?draig Brady wrote: > On 04/08/15 03:13, Guenter Roeck wrote: > > The watchdog infrastructure is currently purely passive, meaning > > it only passes information from user space to drivers and vice versa. > > > > Since watchdog hardware tends to have its own quirks, this can result > > in quite complex watchdog drivers. A number of scanarios are especially common. > > > > - A watchdog is always active and can not be disabled, or can not be disabled > > once enabled. To support such hardware, watchdog drivers have to implement > > their own timers and use those timers to trigger watchdog keepalives while > > the watchdog device is not or not yet opened. > > - A variant of this is the desire to enable a watchdog as soon as its driver > > has been instantiated, to protect the system while it is still booting up, > > but the watchdog daemon is not yet running. > > Just mentioning that patting the watchdog in the boot loader > (by patching grub etc.) can be a more general solution here as it > avoids hangs if the kernel crashes before it runs the watchdog driver, > which is especially true if PXE loaded across the net for example. > Also this tends to be better spaced between boot start and user space loading. the watchdog I'm currently working with on a powerpc platform has a unchangable timeout of ~1 s. To make the machine boot I patched the bootloader and need some automatic pinging in the kernel before userspace takes over. Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-K?nig | Industrial Linux Solutions | http://www.pengutronix.de/ | -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/