public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Niraj kumar <niraj17@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [QUESTION] Where can I get lockstat/lockdep userspace tools
Date: Wed, 15 Oct 2008 16:35:02 +0200	[thread overview]
Message-ID: <1224081302.28131.9.camel@twins> (raw)
In-Reply-To: <b82a89170810150720p2d5ab5efnd6c5ef0bdbd1a03d@mail.gmail.com>

On Wed, 2008-10-15 at 19:50 +0530, Niraj kumar wrote:
> Hi,
> 
> Can anybody tell me where I can get the userspace tools (similar to
> what Solaris has) for working with lockstat/lockdep feature in kernel.

cat, grep, awk has always been plenty powerful to work with the
various /proc files provided by lockdep/lockstat.

Not knowing anything about solaris, nor really caring about it, I'm
afraid you have to be more specific about that you want.



      reply	other threads:[~2008-10-15 14:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-15 14:20 [QUESTION] Where can I get lockstat/lockdep userspace tools Niraj kumar
2008-10-15 14:35 ` Peter Zijlstra [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1224081302.28131.9.camel@twins \
    --to=peterz@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=niraj17@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox