RTOS/rtems
1
0
Fork 0
forked from Imagelibrary/rtems
Code Pull Requests Activity

score: Use Resource Handler for MrsP semaphores

Browse Source 
This enables proper resource dependency tracking and as a side-effect
deadlock detection.
This commit is contained in:
Sebastian Huber
2014-05-26 16:02:58 +02:00
parent 3045738843
commit 9553e7a60d
4 changed files with 410 additions and 36 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
doc/user/sem.t
View File

@@ -751,6 +751,10 @@ willing to be blocked waiting for the semaphore. If it is set to
If the semaphore is available or the @code{@value{RPREFIX}NO_WAIT} option
component is set, then timeout is ignored.
Deadlock situations are detected for MrsP semaphores and the
@code{@value{RPREFIX}UNSATISFIED} status code will be returned on SMP
configurations in this case.
@subheading NOTES:
The following semaphore acquisition option constants
are defined by RTEMS:
@@ -806,7 +810,8 @@ procedure Semaphore_Release (
@subheading DIRECTIVE STATUS CODES:
@code{@value{RPREFIX}SUCCESSFUL} - semaphore released successfully@*
@code{@value{RPREFIX}INVALID_ID} - invalid semaphore id@*
@code{@value{RPREFIX}NOT_OWNER_OF_RESOURCE} - calling task does not own semaphore
@code{@value{RPREFIX}NOT_OWNER_OF_RESOURCE} - calling task does not own semaphore@*
@code{@value{RPREFIX}INCORRECT_STATE} - invalid unlock order
@subheading DESCRIPTION:
@@ -838,6 +843,10 @@ calling task having its priority lowered. This will occur if
the calling task holds no other binary semaphores and it has
inherited a higher priority.
The MrsP semaphores must be released in the reversed obtain order, otherwise
the @code{@value{RPREFIX}INCORRECT_STATE} status code will be returned on SMP
configurations in this case.
@c
@c
@c