Browse Source
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>pull/45011/head
1 changed files with 0 additions and 4 deletions
Loading…
Reference in new issue