Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030353AbVJETuM (ORCPT ); Wed, 5 Oct 2005 15:50:12 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030352AbVJETuL (ORCPT ); Wed, 5 Oct 2005 15:50:11 -0400 Received: from prgy-npn1.prodigy.com ([207.115.54.37]:7434 "EHLO oddball.prodigy.com") by vger.kernel.org with ESMTP id S1030351AbVJETuJ (ORCPT ); Wed, 5 Oct 2005 15:50:09 -0400 Message-ID: <43442E8E.1090301@tmr.com> Date: Wed, 05 Oct 2005 15:50:38 -0400 From: Bill Davidsen User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.11) Gecko/20050729 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Eric W. Biederman" CC: linux-kernel@vger.kernel.org, fastboot@osdl.org Subject: Re: i386 nmi_watchdog: Merge check_nmi_watchdog fixes from x86_64 References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 786 Lines: 18 Eric W. Biederman wrote: > The per cpu nmi watchdog timer is based on an event counter. > idle cpus don't generate events so the NMI watchdog doesn't fire > and the test to see if the watchdog is working fails. Question: given all the concern about reducing clocks and all, do we actually need nmi on more than one CPU? Are there cases where a single CPU hangs in idle on an SMP system? -- -bill davidsen (davidsen@tmr.com) "The secret to procrastination is to put things off until the last possible moment - but no longer" -me - 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/