From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1423113AbXDXVCl (ORCPT ); Tue, 24 Apr 2007 17:02:41 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1423114AbXDXVCl (ORCPT ); Tue, 24 Apr 2007 17:02:41 -0400 Received: from gateway-1237.mvista.com ([63.81.120.158]:64419 "EHLO gateway-1237.mvista.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1423113AbXDXVCk (ORCPT ); Tue, 24 Apr 2007 17:02:40 -0400 Subject: Re: [patch 1/4] Ignore stolen time in the softlockup watchdog From: Daniel Walker To: Ingo Molnar Cc: Jeremy Fitzhardinge , Andrew Morton , Prarit Bhargava , Rick Lindsley , john stultz , Linux Kernel , Eric Dumazet , virtualization@lists.osdl.org, Chris Lalancette , Paul Mackerras , Martin Schwidefsky , Thomas Gleixner In-Reply-To: <20070424205918.GA25383@elte.hu> References: <20070327214919.800272641@goop.org> <20070327215827.871954359@goop.org> <20070423234910.50149faf.akpm@linux-foundation.org> <462E43A7.1050001@goop.org> <20070424105738.e0ce36a9.akpm@linux-foundation.org> <462E4969.6070802@goop.org> <20070424113222.ed2e1314.akpm@linux-foundation.org> <462E61F1.7060403@goop.org> <462E6778.7070305@goop.org> <1177447948.12796.66.camel@imap.mvista.com> <20070424205918.GA25383@elte.hu> Content-Type: text/plain Date: Tue, 24 Apr 2007 14:01:14 -0700 Message-Id: <1177448474.12796.69.camel@imap.mvista.com> Mime-Version: 1.0 X-Mailer: Evolution 2.8.3 (2.8.3-2.fc6) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2007-04-24 at 22:59 +0200, Ingo Molnar wrote: > * Daniel Walker wrote: > > > On Tue, 2007-04-24 at 13:24 -0700, Jeremy Fitzhardinge wrote: > > > > > And sched_clock's use of local_irq_save/restore appears to be absolutely > > > correct, so I think it must be triggering a bug in either the self-tests > > > or lockdep itself. > > > > Why does sched_clock need to disable interrupts? > > i concur. To me it appears not "absolutely correct" that someone > apparently added local_irq_save/restore to sched_clock(), but "absolute > madness". sched_clock() is _very_ performance-sensitive for the > scheduler, do not mess with it. It looks like it's used in some sort of warp check, but only when jiffies is used .. So I'm totally stumped why it's in there.. Daniel