From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: "Alan D. Brunelle" <Alan.Brunelle@hp.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: /proc/lock_stat "stuck"
Date: Wed, 21 May 2008 11:16:20 +0200 [thread overview]
Message-ID: <1211361380.6463.63.camel@lappy.programming.kicks-ass.net> (raw)
In-Reply-To: <483313DD.2020904@hp.com>
On Tue, 2008-05-20 at 14:09 -0400, Alan D. Brunelle wrote:
> I'm attempting to use /proc/lock_stat to gather some information during
> some benchmarking runs, but what I find happens is as follows:
>
> 1. I boot the system - 2.6.26-rc3 kernel + CONFIG_LOCK_STAT=y
>
> 2. I can then look at /proc/lock_stat, and it has valid-looking values
>
> 3. I wait a while, do some stuff, but when I look at /proc/lock_stat
> again the values have not changed.
>
> 4. If I clear the counters - echo 0 > /proc/lock_stat - the counters
> never increase, and no information besides the headers are output when I
> cat /proc/lock_stat.
>
>
> Is there something that one needs to do to get counter updates?
Did you get lockdep warnings? Those disable all lock debugging,
including lockstat.
next prev parent reply other threads:[~2008-05-21 9:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 18:09 /proc/lock_stat "stuck" Alan D. Brunelle
2008-05-21 9:16 ` Peter Zijlstra [this message]
2008-05-21 11:09 ` Alan D. Brunelle
2008-05-21 11:29 ` Peter Zijlstra
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=1211361380.6463.63.camel@lappy.programming.kicks-ass.net \
--to=a.p.zijlstra@chello.nl \
--cc=Alan.Brunelle@hp.com \
--cc=linux-kernel@vger.kernel.org \
/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