From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758359AbYEELdH (ORCPT ); Mon, 5 May 2008 07:33:07 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755258AbYEELcz (ORCPT ); Mon, 5 May 2008 07:32:55 -0400 Received: from mx3.mail.elte.hu ([157.181.1.138]:60668 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755120AbYEELcy (ORCPT ); Mon, 5 May 2008 07:32:54 -0400 Date: Mon, 5 May 2008 13:32:31 +0200 From: Ingo Molnar To: David Miller Cc: a.p.zijlstra@chello.nl, tglx@linutronix.de, guichaz@gmail.com, andi@firstfloor.org, linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, efault@gmx.de, dhaval@linux.vnet.ibm.com Subject: Re: [RFC][PATCH] sched_clock_cpu() Message-ID: <20080505113231.GA13915@elte.hu> References: <1209832169.6929.42.camel@lappy> <20080503170130.GB21967@elte.hu> <20080503.212607.157994166.davem@davemloft.net> <20080504090024.GA29318@elte.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080504090024.GA29318@elte.hu> User-Agent: Mutt/1.5.17 (2007-11-01) X-ELTE-VirusStatus: clean X-ELTE-SpamScore: -1.5 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.5 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.3 -1.5 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Ingo Molnar wrote: > > * David Miller wrote: > > > > that wont work very well when sched_clock() is called from within > > > CONFIG_LOCK_STAT instrumentation. Does the patch below solve the > > > boot problems for you? > > > > Also, no platform can set HAVE_STABLE_CLOCK until we instantiate it in > > a Kconfig somewhere. I've choosen to do it in kernel/Kconfig.hz and > > here are the sparc/sparc64 bits as well, I've booted this up with > > Peter's patch on my 64-cpu niagara2 box and done some basic testing. > > applied, thanks David. > > right now this topic looks good in review and in testing but it is > stalled on a bug: in overnight testing it triggered an ftrace > self-test hang that i bisected down to that patch. While that doesnt > affect mainline it's something that shows that the new sched_clock() > code is not as widely usable as the old code - have to investigate > that some more. FYI, figured that out today and fixed it, so the topic has green lights again. Ingo