From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ozlabs.org (ozlabs.org [203.10.76.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mx.ozlabs.org", Issuer "CA Cert Signing Authority" (verified OK)) by bilbo.ozlabs.org (Postfix) with ESMTPS id DB8F3B6F20 for ; Wed, 19 Aug 2009 21:23:32 +1000 (EST) Received: from casper.infradead.org (casper.infradead.org [85.118.1.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id 68454DDD0B for ; Wed, 19 Aug 2009 21:23:32 +1000 (EST) Subject: Re: spin_is_locked() broken for uniprocessor? From: Peter Zijlstra To: Leon Woestenberg In-Reply-To: References: <7099.1250674686@redhat.com> <20090819115301.563be6da@lxorguk.ukuu.org.uk> Content-Type: text/plain Date: Wed, 19 Aug 2009 13:23:13 +0200 Message-Id: <1250680993.7583.350.camel@twins> Mime-Version: 1.0 Cc: Steven Rostedt , Linux-Kernel List , linuxppc-dev list , Thomas Gleixner , Ingo Molnar , Alan Cox List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, 2009-08-19 at 13:16 +0200, Leon Woestenberg wrote: > Hello, > > On Wed, Aug 19, 2009 at 12:53 PM, Alan Cox wrote: > > On Wed, 19 Aug 2009 10:38:06 +0100 > > > > in drivers because there is driver code that uses spin_is_locked() in > > fairly sensible fashion when dealing with locking. > > > One use is to measure lock contention hits on a particular spin lock. > > > However I wonder if there are tracing capabilities to measure lock > contention on a particular lock? lock_stat no good for you?