On Tue, 2008-05-20 at 14:09 -0400, Alan D. Brunelle wrote:
quoted text
> 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.

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