Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757341AbYJPVfO (ORCPT ); Thu, 16 Oct 2008 17:35:14 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750972AbYJPVfA (ORCPT ); Thu, 16 Oct 2008 17:35:00 -0400 Received: from casper.infradead.org ([85.118.1.10]:47338 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753799AbYJPVfA (ORCPT ); Thu, 16 Oct 2008 17:35:00 -0400 Subject: Re: tracepoints for kernel/mutex.c From: Peter Zijlstra To: Jason Baron Cc: linux-kernel@vger.kernel.org, compudj@krystal.dyndns.org, fche@redhat.com, fweisbec@gmail.com, edwintorok@gmail.com, mingo@elte.hu, Steven Rostedt In-Reply-To: <20081016210430.GC25738@redhat.com> References: <20081016210430.GC25738@redhat.com> Content-Type: text/plain Date: Thu, 16 Oct 2008 23:34:38 +0200 Message-Id: <1224192879.16038.82.camel@lappy.programming.kicks-ass.net> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1476 Lines: 33 On Thu, 2008-10-16 at 17:04 -0400, Jason Baron wrote: > Below are 3 tracepoints I've been playing with in kernel/mutex.c using > a SystemTap script. The idea is to detect and determine the cause of > lock contention. Currently I get the following output: > >