Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030946AbXFHR2S (ORCPT ); Fri, 8 Jun 2007 13:28:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S969179AbXFHR2G (ORCPT ); Fri, 8 Jun 2007 13:28:06 -0400 Received: from viefep18-int.chello.at ([213.46.255.22]:36283 "EHLO viefep16-int.chello.at" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S969322AbXFHR2E (ORCPT ); Fri, 8 Jun 2007 13:28:04 -0400 Subject: Re: [RFC] [Patch 4/4] lock contention tracking slimmed down From: Peter Zijlstra To: Martin Peschke Cc: linux-kernel@vger.kernel.org, jbaron@redhat.com, rostedt@goodmis.org, billh@gnuppy.monkey.org, mingo@elte.hu, linux-s390@vger.kernel.org In-Reply-To: <46698F7F.4090407@de.ibm.com> References: <1181165656.7133.23.camel@dix> <1181202258.7348.217.camel@twins> <46698B1D.3000806@de.ibm.com> <1181322460.5728.2.camel@lappy> <46698F7F.4090407@de.ibm.com> Content-Type: text/plain Date: Fri, 08 Jun 2007 19:27:02 +0200 Message-Id: <1181323622.5728.6.camel@lappy> Mime-Version: 1.0 X-Mailer: Evolution 2.10.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1593 Lines: 37 On Fri, 2007-06-08 at 19:18 +0200, Martin Peschke wrote: > Peter Zijlstra wrote: > > On Fri, 2007-06-08 at 19:00 +0200, Martin Peschke wrote: > >> Peter Zijlstra wrote: > >>> I'm confused as to where the class->stat objects are initialised? Is > >>> that done in lock_stat_init()? If so, then you have a bug. > >> static struct lock_class lock_classes[MAX_LOCKDEP_KEYS]; > >> > >> I assume this gets us class structures containing all zeros, doesn't it? > >> Then class->stat is zeros as well, which is handled by lib/statistics. > >> (In this case, data gathering hasn't been turned on yet, and statistic_inc() > >> and similar functions don't access other areas of struct statistic.) > > > > Who eventually calls percpu_alloc? > > There is a small state machine calling percpu_alloc when users do > > echo state=on > /debug/statistics/lockdep/definition > > So data gathering is off by default. > > It might make sense to allow "state=on" as a default. Then allocation would > be done in the context of statistic_attach(). Right, the problem here is that you iterate over all_lock_classes once at init. Contrary to what the name might suggest, it are not all possible classes, just all active ones. So you'll only attach the classes which have been used up until the init point. All other classes used later will never be initialized. - 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/