Re: interrupt checks for spinlocks

Davide Libenzi (davidel@xmailserver.org)
Mon, 4 Nov 2002 07:47:22 -0800 (PST)


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

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