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

New ideas on test incorporated.

Browse Source
This commit is contained in:
Joel Sherrill
1999-10-26 02:32:47 +00:00
parent 99826740e2
commit 2ca64b55ea
1 changed files with 17 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

26
c/src/tests/sptests/sp27/TODO
View File

@@ -2,18 +2,26 @@
# $Id$ # $Id$
# #
This test should be for rtems_semaphore_flush. It will be something like: This test will be for rtems_semaphore_flush once it is written.
To avoid scheduling problems in the printout, it would be better to
have the test program:
volatile int bFlag, cFlag;
TaskA: TaskA:
create semaphore with initial count 0 create semaphore with initial count 0
start taskB and TaskC (Higher priority than taskA, no round-robin) start taskB and TaskC (Higher priority than taskA, no
print message round-robin)
semaphore_flush print bFlag, cFlag (should both be 0)
semaphore_flush
print bFlag, cFlag (should both be 1)
TaskB/C: TaskB/C:
obtain semaphore obtain semaphore
print message set flag (B or C as appropriate)
suspend/delete self suspend/delete self
Successful test would show message from both tasks B and C after the Successful test would show message from both tasks B and C after the
message from task A. message from task A.