Messages in this thread | | | Date | Tue, 7 Dec 1999 17:41:59 -0500 | From | Johannes Erdfelt <> | Subject | Re: deadlock avoidance? |
| |
On Tue, Dec 07, 1999, Davide Libenzi <dlibenzi@maticad.it> wrote: > Every task has a pid, and since interrupt code is executed by the current > task in kernel mode, interrupt code has a pid. > It's the same concept implemented in NT's CRITICAL_SECTIONs : a process can > call more times EnterCriticalSection() provided that it calls the same > number of LeaveCriticalSection().
Well, more importantly, does it have a unique pid?
If an irq interrupts a process which legally has the lock acquired we'll have problems.
JE
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |