From: Robert Love <rml@tech9.net>
To: "David S. Miller" <davem@redhat.com>
Cc: manfred@colorfullife.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] improve spinlock debugging
Date: 03 Dec 2001 23:30:15 -0500 [thread overview]
Message-ID: <1007440220.1303.14.camel@phantasy> (raw)
In-Reply-To: <20011203.202130.118628301.davem@redhat.com>
In-Reply-To: <3C0BDC33.6E18C815@colorfullife.com> <20011203.202130.118628301.davem@redhat.com>
On Mon, 2001-12-03 at 23:21, David S. Miller wrote:
> Keep track of how many locks are being held at once, and check if it
> is zero at switch_to() time. You can also do this to measure things
> like max number of locks held at once and other statistics.
>
> I added the first bit to sparc64 while hunting down a bug.
Another interesting idea is see if a lock is held during a call to
udelay.
Once you get a lock count, a lot is possible. I have looked into doing
some of these tests with the preemptible kernel patch. Since the
preemption count is essential the lock depth, we have quick access to
all this data.
Robert Love
next prev parent reply other threads:[~2001-12-04 4:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-03 20:10 [PATCH] improve spinlock debugging Manfred Spraul
2001-12-04 4:21 ` David S. Miller
2001-12-04 4:30 ` Robert Love [this message]
2001-12-04 20:30 ` george anzinger
2001-12-04 20:51 ` Robert Love
2001-12-04 21:25 ` george anzinger
2001-12-04 21:39 ` Robert Love
2001-12-04 22:06 ` Nigel Gamble
2001-12-04 22:23 ` Robert Love
2001-12-05 1:13 ` Roman Zippel
2001-12-05 7:41 ` george anzinger
2001-12-04 20:53 ` Manfred Spraul
2001-12-05 0:54 ` george anzinger
2001-12-04 21:20 ` Nigel Gamble
2001-12-04 21:27 ` george anzinger
2001-12-05 8:47 ` Giuliano Pochini
2001-12-05 15:42 ` Manfred Spraul
[not found] ` <20011219025332.GA18344@krispykreme>
2001-12-20 17:08 ` Manfred Spraul
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=1007440220.1303.14.camel@phantasy \
--to=rml@tech9.net \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.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