Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 8 Nov 2002 15:23:41 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 8 Nov 2002 15:23:40 -0500 Received: from modemcable191.130-200-24.mtl.mc.videotron.ca ([24.200.130.191]:38411 "EHLO montezuma.mastecende.com") by vger.kernel.org with ESMTP id ; Fri, 8 Nov 2002 15:23:37 -0500 Date: Fri, 8 Nov 2002 15:30:02 -0500 (EST) From: Zwane Mwaikambo X-X-Sender: zwane@montezuma.mastecende.com To: "Heater, Daniel (IndSys, GEFanuc, VMIC)" cc: "'Corey Minyard'" , Subject: RE: NMI handling rework In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1157 Lines: 28 On Fri, 8 Nov 2002, Heater, Daniel (IndSys, GEFanuc, VMIC) wrote: > Am I reading this correctly? As long as no one passes back NOTIFY_STOP_MASK, > all handlers are run. Assuming that all external NMI sources have a means of > checking whether they were the source, this would work like shared PCI > interrupts. On Linux we run through all handlers for shared interrupts, it is up to the handler to figure out wether it really was supposed to receive that interrupt (normally quick status checks for hardware). > affected handlers have not run yet and will get run on the current pass, or > they will run on the next pass. You may have two handlers run on a single > pass but you should not drop any. True?? For sanity's sake stick to running through all of them, there should be no partial handling, every registered handler should get serviced once per NMI interrupt. Zwane -- function.linuxpower.ca - 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/