Subject: Re: [PATCH][RFC] Adding information of counts processes acquired
 how many spinlocks to schedstat
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Ingo Molnar <mingo@elte.hu>
Cc: Frederic Weisbecker <fweisbec@gmail.com>, mitake@dcl.info.waseda.ac.jp,
       andi@firstfloor.org, acme@redhat.com, linux-kernel@vger.kernel.org
In-Reply-To: <20090710135032.GA26264@elte.hu>
References: <20090706.142058.56800444.mitake@dcl.info.waseda.ac.jp>
	 <1246870279.8143.4.camel@twins> <20090706115451.GA29715@one.firstfloor.org>
	 <20090710.214547.34380852.mitake@dcl.info.waseda.ac.jp>
	 <1247230336.7529.34.camel@twins> <20090710134307.GB23481@elte.hu>
	 <20090710134625.GB6237@nowhere>  <20090710135032.GA26264@elte.hu>
Content-Type: text/plain
Date: Fri, 10 Jul 2009 15:56:52 +0200
Message-Id: <1247234212.7529.40.camel@twins>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 850
Lines: 22

On Fri, 2009-07-10 at 15:50 +0200, Ingo Molnar wrote:

> > I wonder if the lock_*() events should become independant from 
> > lockdep so that we don't need to always enable lockdep to get the 
> > lock events at the same time.
> > 
> > It could be a separate option.
> 
> They already should be to a large degree if CONFIG_LOCK_STAT is 
> enabled but CONFIG_PROVE_LOCKING is off. In theory :-)

Right, you don't need CONFIG_PROVE_LOCKING in order to get the
tracepoints. Also, you can always boot with prove_locking=0 or runtime
disable it using: echo 0 > /sys/module/lockdep/parameters/prove_locking


--
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/