Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754099AbYJWDgG (ORCPT ); Wed, 22 Oct 2008 23:36:06 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751226AbYJWDfy (ORCPT ); Wed, 22 Oct 2008 23:35:54 -0400 Received: from lobo.ruivo.org ([66.92.68.119]:41193 "EHLO lobo.ruivo.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751086AbYJWDfy (ORCPT ); Wed, 22 Oct 2008 23:35:54 -0400 Date: Wed, 22 Oct 2008 23:35:40 -0400 From: Aristeu Rozanski To: "Maciej W. Rozycki" Cc: Ingo Molnar , Thomas Gleixner , Vivek Goyal , linux-kernel@vger.kernel.org Subject: Re: [RFC][PATCH] nmi watchdog: handle NMI_IO_APIC on nmi_watchdog Message-ID: <20081023033540.GF28317@cathedrallabs.org> References: <20080313180538.GC4620@cathedrallabs.org> <20080321114752.GA25225@elte.hu> <20080326152417.GE25854@cathedrallabs.org> <20080326182333.GA11187@elte.hu> <20081022215008.GE28317@cathedrallabs.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1326 Lines: 32 > > > but this stops all NMIs, not just the IO-APIC generated ones, doesnt it? > > external NMIs would come by LINT1, no? > > Correct. > > > after reading a lot and talking with Vivek, what I understood was that 8259 is > > also connected to LINT0, so timer interrupts would be reported both in > > IOAPIC and on LINT0. LVT0 is being configured on setup_nmi() to generate > > an NMI. Also, the same timer interrupt would generate an regular interrupt > > coming from IOAPIC. Clearing the APIC_DM_NMI on LVT0 would disable the > > NMI delivery, but not the regular interrupt. > > or am I missing something here? > > You are correct. The routing of the 8254 timer interrupt may vary, but > the NMI watchdog it drives, if supported, always uses the LINT0 input of > all the local APICs. thanks > You seem to be writing in reply to a very old thread -- please make sure > your concerns are still valid with current code. For example we have an > implementation of __acpi_nmi_disable() now, which is exactly your proposed > one. didn't noticed that, sorry. -- Aristeu -- 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/