[riot-notifications] [RIOT-OS/RIOT] core/rmutex: use atomic utils (#16919)

Marian Buschsieweke notifications at github.com
Thu Sep 30 11:03:30 CEST 2021


On my Nucleo-F767ZI:

```
$ make BOARD=nucleo-f767zi -C tests/rmutex flash test

[...]

Help: Press s to start test, r to print it is ready
READY
s
START
main(): This is RIOT! (Version: 2021.10-devel-790-g7313a-core/rmutex)
Recursive Mutex test
Please refer to the README.md for more information

T2 (prio 6, depth 0): trying to lock rmutex now
T3 (prio 4, depth 0): trying to lock rmutex now
T4 (prio 5, depth 0): trying to lock rmutex now
T5 (prio 2, depth 0): trying to lock rmutex now
T6 (prio 4, depth 0): trying to lock rmutex now
main: unlocking recursive mutex
T5 (prio 2, depth 0): locked rmutex now
T5 (prio 2, depth 1): trying to lock rmutex now
T5 (prio 2, depth 1): locked rmutex now
T5 (prio 2, depth 2): trying to lock rmutex now
T5 (prio 2, depth 2): locked rmutex now
T5 (prio 2, depth 3): trying to lock rmutex now
T5 (prio 2, depth 3): locked rmutex now
T5 (prio 2, depth 3): unlocked rmutex
T5 (prio 2, depth 2): unlocked rmutex
T5 (prio 2, depth 1): unlocked rmutex
T5 (prio 2, depth 0): unlocked rmutex
T3 (prio 4, depth 0): locked rmutex now
T3 (prio 4, depth 1): trying to lock rmutex now
T3 (prio 4, depth 1): locked rmutex now
T3 (prio 4, depth 2): trying to lock rmutex now
T3 (prio 4, depth 2): locked rmutex now
T3 (prio 4, depth 2): unlocked rmutex
T3 (prio 4, depth 1): unlocked rmutex
T3 (prio 4, depth 0): unlocked rmutex
T6 (prio 4, depth 0): locked rmutex now
T6 (prio 4, depth 1): trying to lock rmutex now
T6 (prio 4, depth 1): locked rmutex now
T6 (prio 4, depth 2): trying to lock rmutex now
T6 (prio 4, depth 2): locked rmutex now
T6 (prio 4, depth 3): trying to lock rmutex now
T6 (prio 4, depth 3): locked rmutex now
T6 (prio 4, depth 4): trying to lock rmutex now
T6 (prio 4, depth 4): locked rmutex now
T6 (prio 4, depth 4): unlocked rmutex
T6 (prio 4, depth 3): unlocked rmutex
T6 (prio 4, depth 2): unlocked rmutex
T6 (prio 4, depth 1): unlocked rmutex
T6 (prio 4, depth 0): unlocked rmutex
T4 (prio 5, depth 0): locked rmutex now
T4 (prio 5, depth 1): trying to lock rmutex now
T4 (prio 5, depth 1): locked rmutex now
T4 (prio 5, depth 2): trying to lock rmutex now
T4 (prio 5, depth 2): locked rmutex now
T4 (prio 5, depth 2): unlocked rmutex
T4 (prio 5, depth 1): unlocked rmutex
T4 (prio 5, depth 0): unlocked rmutex
T2 (prio 6, depth 0): locked rmutex now
T2 (prio 6, depth 1): trying to lock rmutex now
T2 (prio 6, depth 1): locked rmutex now
T2 (prio 6, depth 2): trying to lock rmutex now
T2 (prio 6, depth 2): locked rmutex now
T2 (prio 6, depth 3): trying to lock rmutex now
T2 (prio 6, depth 3): locked rmutex now
T2 (prio 6, depth 4): trying to lock rmutex now
T2 (prio 6, depth 4): locked rmutex now

$ echo $?
0
```

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/pull/16919#issuecomment-931092332
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20210930/d5704d87/attachment-0001.htm>


More information about the notifications mailing list