mirror of
https://github.com/RIOT-OS/RIOT.git
synced 2024-12-29 04:50:03 +01:00
eb1279005c
Replace direct accesses to sched_active_thread and sched_active_pid with the helper functions thread_getpid() and thread_get_active(). This serves two purposes: 1. It makes accidental writes to those variable from outside core less likely. 2. Casting off the volatile qualifier is now well contained to those two functions |
||
|---|---|---|
| .. | ||
| tests | ||
| main.c | ||
| Makefile | ||
| Makefile.ci | ||
| README.md | ||
Expected result
When successful, you should see 5 different threads printing their PID and priority. The thread with the lowest priority should be able to lock (and unlock) the mutex first, followed by the other threads in the order of their priority (highest next). The output should look like the following:
main(): This is RIOT! (Version: xxx)
Mutex order test
Please refer to the README.md for more information
T3 (prio 6): trying to lock mutex now
T4 (prio 4): trying to lock mutex now
T5 (prio 0): trying to lock mutex now
T6 (prio 2): trying to lock mutex now
T7 (prio 1): trying to lock mutex now
T5 (prio 0): unlocking mutex now
T7 (prio 1): unlocking mutex now
T6 (prio 2): unlocking mutex now
T4 (prio 4): unlocking mutex now
T3 (prio 6): unlocking mutex now
Test END, check the order of priorities above.
Background
This test application stresses a mutex with a number of threads waiting on it.