Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 20 Feb 2001 16:02:51 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 20 Feb 2001 16:02:41 -0500 Received: from nat-pool.corp.redhat.com ([199.183.24.200]:38793 "EHLO devserv.devel.redhat.com") by vger.kernel.org with ESMTP id ; Tue, 20 Feb 2001 16:02:39 -0500 Date: Tue, 20 Feb 2001 16:00:53 -0500 (EST) From: Ingo Molnar X-X-Sender: To: Alan Cox cc: Mikael Pettersson , , Subject: Re: [PATCH] 2.4.1-ac UP-APIC updates 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 On Tue, 20 Feb 2001, Alan Cox wrote: > > i dont like this one. 100 times a second makes absolutely no performance > > difference whatsoever - but eg. i'm driving kernel profiling from the NMI > > handler to get profiles of eg. IRQ handlers and other cli()-ed code areas. > > So set it to 100Hz as a debugging option like slab debugging my major gripe right now is that we still have bug reports that say that systems hang when using nmi_watchdog=1 and work if nmi_watchdog=0. Changing the NMI watchdog to be 1 Hz will make these bugreports "Linux hangs once a week" instead of a "Linux hangs after 1-2 hours", which is clearly hiding things and making debugging harder. (and driving kernel-profiling from the NMI interrupt is a short-term patch, so there is just no point in going to 1 Hz right now just to go back to 100 Hz a few days later.) the rest of the changes are excellent - it's only the 100 Hz NMI issue i have a problem with. Ingo - 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/