Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261636AbVEOODn (ORCPT ); Sun, 15 May 2005 10:03:43 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261641AbVEOODm (ORCPT ); Sun, 15 May 2005 10:03:42 -0400 Received: from colin.muc.de ([193.149.48.1]:33550 "EHLO mail.muc.de") by vger.kernel.org with ESMTP id S261636AbVEOODa (ORCPT ); Sun, 15 May 2005 10:03:30 -0400 Date: 15 May 2005 16:03:26 +0200 Date: Sun, 15 May 2005 16:03:26 +0200 From: Andi Kleen To: Dave Jones , akpm@osdl.org, linux-kernel@vger.kernel.org Subject: Re: tickle nmi watchdog whilst doing serial writes. Message-ID: <20050515140326.GA94354@muc.de> References: <20050513184806.GA24166@redhat.com> <20050515130742.A29619@flint.arm.linux.org.uk> <20050515150103.B29619@flint.arm.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050515150103.B29619@flint.arm.linux.org.uk> User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 865 Lines: 21 On Sun, May 15, 2005 at 03:01:03PM +0100, Russell King wrote: > On Sun, May 15, 2005 at 02:20:14PM +0200, Andi Kleen wrote: > > Then someone needs to convince Linus to export touch_nmi_watchdog > > again. > > > > Or how about checking if interrupts are off here (iirc we have > > a generic function for that now) and then using > > a smaller timeout and otherwise schedule_timeout() ? > > The interrupt state doesn't tell us whether we can schedule. It > tells us when we can't schedule, which is different from when we > can. For example: Yes, you're right of course. Must have not been thinking clearly. -Andi - 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/