Messages in this thread | | | Date | Sun, 3 Nov 2002 17:39:37 -0800 | From | William Lee Irwin III <> | Subject | Re: interrupt checks for spinlocks |
| |
On Sun, Nov 03, 2002 at 05:39:29PM -0800, Davide Libenzi 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 ...
Then you had something different in mind. I *thought* you meant maintaining a graph's arcs and dumping the specific deadlocking processes and their acquired locks at failure time. This scheme with limited reporting requires less work/code, but is still beyond the scope of what I was doing.
Bill - 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/
| |