From 1f8301a97296178c772fcf42ae1d2e78b9ac40a8 Mon Sep 17 00:00:00 2001 From: Sebastian Huber Date: Mon, 15 Jun 2020 14:13:48 +0200 Subject: c-user: Mention possible preemptions Mention that object create/delete may case the calling task to be preempted due to the object allocator mutex. --- c-user/semaphore_manager.rst | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) (limited to 'c-user/semaphore_manager.rst') diff --git a/c-user/semaphore_manager.rst b/c-user/semaphore_manager.rst index 3e6008d..13058f3 100644 --- a/c-user/semaphore_manager.rst +++ b/c-user/semaphore_manager.rst @@ -376,7 +376,8 @@ DESCRIPTION: are serviced in First In-First Out order. NOTES: - This directive will not cause the calling task to be preempted. + This directive may cause the calling task to be preempted due to an + obtain and release of the object allocator mutex. The priority inheritance and priority ceiling algorithms are only supported for local, binary semaphores that use the priority task wait queue blocking @@ -523,6 +524,9 @@ DESCRIPTION: this semaphore is reclaimed by RTEMS. NOTES: + This directive may cause the calling task to be preempted due to an + obtain and release of the object allocator mutex. + The calling task will be preempted if it is enabled by the task's execution mode and a higher priority local task is waiting on the deleted semaphore. The calling task will NOT be preempted if all of the tasks that are waiting -- cgit v1.2.3