Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755560AbZKDLql (ORCPT ); Wed, 4 Nov 2009 06:46:41 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755415AbZKDLql (ORCPT ); Wed, 4 Nov 2009 06:46:41 -0500 Received: from mx2.mail.elte.hu ([157.181.151.9]:56118 "EHLO mx2.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755244AbZKDLqk (ORCPT ); Wed, 4 Nov 2009 06:46:40 -0500 Date: Wed, 4 Nov 2009 12:46:30 +0100 From: Ingo Molnar To: Aristeu Rozanski , Thomas Gleixner , "H. Peter Anvin" , Peter Zijlstra , =?iso-8859-1?Q?Fr=E9d=E9ric?= Weisbecker Cc: linux-kernel@vger.kernel.org Subject: Re: [PATCH 2/2] x86: introduce NMI_AUTO as nmi_watchdog option Message-ID: <20091104114630.GA16993@elte.hu> References: <20091103171054.GB25437@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091103171054.GB25437@redhat.com> User-Agent: Mutt/1.5.19 (2009-01-05) X-ELTE-SpamScore: 0.0 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=0.0 required=5.9 tests=none autolearn=no SpamAssassin version=3.2.5 _SUMMARY_ Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1588 Lines: 35 * Aristeu Rozanski wrote: > NMI_AUTO is a new nmi_watchdog option that makes LAPIC be tried first > and if the CPU isn't supported, IOAPIC will be used. It's useful in > cases where NMI watchdog is enabled by default in a kernel built for > different machines. It can be configured by default or selected with > nmi_watchdog=3 or nmi_watchdog=auto parameters. What i'd like to see for the NMI watchdog is much more ambitious than this: the use of perf events to run a periodic NMI callback. The NMI watchdog would cause the creation of a per-cpu perf_event structure (in-kernel). All x86 CPUs that have perf event support (the majority of them) will thus be able to have an NMI watchdog using a nice, generic piece of code and we'd be able to phase out the open-coded NMI watchdog code. The user would not notice much from this: we'd still have the /proc/sys/kernel/nmi_watchdog toggle to turn it on/off, and we'd still have the nmi_watchog= boot parameter as well. But the underlying implementation would be far more generic and far more usable than the current code. Would you be interested in moving the NMI watchdog code in this direction? Most of the perf events changes (callbacks, helpers for in-kernel event allocations, etc.) are in latest -tip already, so you could use that as a base. 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/