e9b288b713
Removes an unnecessary schedule lock/unlock pair from k_mutex_unlock(). Rationale: Given that only the current thread (which would also be the mutex owner) will be able to modify the mutex object AND that a recursive unlock ought never trigger any reschedule (as it does not touch the pend queue), then performing a schedule lock is not needed prior to testing for a recursive unlock. Furthermore, even if it is not a recursive unlock, then a schedule lock is superfluous as the existing spinlock provides sufficient protection. Signed-off-by: Peter Mitsis <peter.mitsis@intel.com> |
||
|---|---|---|
| .. | ||
| include | ||
| paging | ||
| CMakeLists.txt | ||
| Kconfig | ||
| Kconfig.vm | ||
| atomic_c.c | ||
| banner.c | ||
| cache_handlers.c | ||
| compiler_stack_protect.c | ||
| condvar.c | ||
| device.c | ||
| errno.c | ||
| events.c | ||
| fatal.c | ||
| futex.c | ||
| idle.c | ||
| init.c | ||
| kheap.c | ||
| mailbox.c | ||
| main_weak.c | ||
| mem_domain.c | ||
| mem_slab.c | ||
| mempool.c | ||
| mmu.c | ||
| msg_q.c | ||
| mutex.c | ||
| pipes.c | ||
| poll.c | ||
| queue.c | ||
| sched.c | ||
| sem.c | ||
| smp.c | ||
| stack.c | ||
| system_work_q.c | ||
| thread.c | ||
| timeout.c | ||
| timer.c | ||
| usage.c | ||
| userspace.c | ||
| userspace_handler.c | ||
| version.c | ||
| work.c | ||
| xip.c | ||