From: Davide Libenzi <davidel@xmailserver.org>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: William Lee Irwin III <wli@holomorphy.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
<hch@lst.de>, Benjamin LaHaise <bcrl@redhat.com>
Subject: Re: interrupt checks for spinlocks
Date: Mon, 4 Nov 2002 07:47:22 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.44.0211040746250.1745-100000@blue1.dev.mcafeelabs.com> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0211032117190.10796-100000@dragon.pdx.osdl.net>
On Sun, 3 Nov 2002, Randy.Dunlap wrote:
> | It's not realy a graph Bill. Each task has a list of acquired locks (
> | by address ). You keep __LINE__ and __FILE__ with you list items. When
> | there's a deadlock you'll have somewhere :
> |
> | TSK#N TSK#M
> | -------------
> | ... ...
> | LCK#I LCK#J
> | ... ...
> | -> LCK#J LCK#I
> |
> | Then with a SysReq key you dump the list of acquired locks for each task
> | who's spinning for a lock. IMO it might be usefull ...
>
> What's a task in this context? Are we (you) talking about
> kernel threads/drivers etc. or userspace?
Hi Randy,
a task here is anything you can identify with a task_struct*
- Davide
next prev parent reply other threads:[~2002-11-04 15:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-03 22:08 William Lee Irwin III
2002-11-04 0:15 ` Davide Libenzi
2002-11-04 0:39 ` William Lee Irwin III
2002-11-04 1:39 ` Davide Libenzi
2002-11-04 1:39 ` William Lee Irwin III
2002-11-04 5:18 ` Randy.Dunlap
2002-11-04 15:47 ` Davide Libenzi [this message]
2002-11-04 13:31 ` Alan Cox
[not found] <mailman.1036362421.16883.linux-kernel2news@redhat.com>
[not found] ` <200211040028.gA40S8600593@devserv.devel.redhat.com>
[not found] ` <20021104002813.GZ16347@holomorphy.com>
2002-11-04 0:42 ` Pete Zaitcev
2002-11-04 0:53 ` William Lee Irwin III
2002-11-04 1:18 ` Robert Love
2002-11-04 1:42 ` William Lee Irwin III
2002-11-04 3:01 ` Robert Love
2002-11-04 3:04 ` William Lee Irwin III
2002-11-04 3:22 ` William Lee Irwin III
2002-11-04 3:36 ` Zwane Mwaikambo
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=Pine.LNX.4.44.0211040746250.1745-100000@blue1.dev.mcafeelabs.com \
--to=davidel@xmailserver.org \
--cc=bcrl@redhat.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=wli@holomorphy.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
all inboxes | Powered by JetHome®