Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 21 Jan 2003 12:36:29 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 21 Jan 2003 12:36:29 -0500 Received: from noodles.codemonkey.org.uk ([213.152.47.19]:13780 "EHLO noodles.internal") by vger.kernel.org with ESMTP id ; Tue, 21 Jan 2003 12:36:28 -0500 Date: Tue, 21 Jan 2003 17:42:37 +0000 From: Dave Jones To: Joel Becker Cc: lkml , Andrew Morton , Linus Torvalds , Wim Coekaerts Subject: Re: [PATCH][2.5] hangcheck-timer Message-ID: <20030121174237.GB13480@codemonkey.org.uk> Mail-Followup-To: Dave Jones , Joel Becker , lkml , Andrew Morton , Linus Torvalds , Wim Coekaerts References: <20030121011954.GO20972@ca-server1.us.oracle.com> <20030121125039.GA5997@codemonkey.org.uk> <20030121174001.GV20972@ca-server1.us.oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030121174001.GV20972@ca-server1.us.oracle.com> User-Agent: Mutt/1.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 21, 2003 at 09:40:02AM -0800, Joel Becker wrote: > > I'm puzzled. What does this do that softdog.c doesn't ? > > First, softdog.c requires userspace interaction. Second, softdog.c > relies on jiffies. If the system goes out to lunch via udelay() or > another hardware call that freezes the CPUs for a bit, jiffies does not > increment. The system could be frozen for two minutes (qla2x00 used to > do this for 90 seconds) and softdog.c never notices, because jiffies > hasn't counted a single second during this time. Ok, seems to make sense now, thanks. Wouldn't this belong under drivers/char/watchdog too though ? It seems very 'watchdog-ish' to me. Dave -- | Dave Jones. http://www.codemonkey.org.uk | SuSE Labs - 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/