Lephe
7aa86235a3
The function was designed with multi-threaded concurrency in mind, where threads can take over while the lock is held and simply block trying to acquire it, which allows the lock holder to proceed. However interrupt handlers are different; they have priority, so once they start they must complete immediately. The cannot afford to block on the lock as the program would simply freeze. In exchange, they clean up before they leave, so there are some guarantees on the execution state even when interrupted. The correct protection is therefore not a lock but a temporary block on interrupts. There is no data race on the value of the saved IMASK because it is preserved during interrupt handling. |
||
|---|---|---|
| .. | ||
| atomic.c | ||
| cpu.c | ||
| registers.s | ||
| sleep.c | ||