All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yong Zhang <yong.zhang@windriver.com>
To: Darren Hart <dvhltc@us.ibm.com>
Cc: "lkml, " <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: Lockdep usage
Date: Thu, 22 Apr 2010 15:06:25 +0800	[thread overview]
Message-ID: <20100422070625.GA17515@windriver.com> (raw)
In-Reply-To: <4BCFEBFF.4090505@us.ibm.com>

On Wed, Apr 21, 2010 at 11:26:07PM -0700, Darren Hart wrote:
> I'm having some trouble with lockstat. I've enabled
> CONFIG_LOCK_STATS and then run the following commands to collect the
> lock statistics for the futex_lock test case. I expect this test
> case to generate a fair amount of contention on the futex hash
> bucket locks, but they don't show up in the stats (in fact, nothing
> shows up in the stats). I have seen much longer lock_stat files when
> I forgot to clear them before the test, but no hb locks showed up
> there either.
> 
> Is my usage below incorrect? Do I have to somehow annotate the
> hb->lock in order for lockstat to track it?

IMHO, you don't need to do that.

> lock.lockstat; echo 0 > /proc/sys/kernel/lock_stat
> futex_lock: Measure FUTEX_LOCK operations per second
>         Arguments: iterations=10000000 threads=256 adaptive=no
>                    period=1000 duty-cycle=20%
> Result: 731 Kiter/s
> 
> # cat lock.lockstat
> lock_stat version 0.3
> *WARNING* lock debugging disabled!! - possibly due to a lockdep warning

This means lockdep has detect there is something wrong.
Can you show your 'dmesg'?

Thanks,
Yong

> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>                               class name    con-bounces
> contentions   waittime-min   waittime-max waittime-total
> acq-bounces acquisitions   holdtime-min   holdtime-max
> holdtime-total
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> 
> #
> 
> Thanks,
> 
> -- 
> Darren Hart
> IBM Linux Technology Center
> Real-Time Linux Team
> --
> 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/

  reply	other threads:[~2010-04-22  7:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-22  6:26 Lockdep usage Darren Hart
2010-04-22  7:06 ` Yong Zhang [this message]
2010-04-22 14:57   ` Darren Hart
2010-04-23  0:34     ` Jiri Kosina
2010-04-23 14:35       ` Darren Hart

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=20100422070625.GA17515@windriver.com \
    --to=yong.zhang@windriver.com \
    --cc=dvhltc@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.