c/src/tests/sptests/sp27/TODO


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27

#
#  $Id$
#

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:
         create semaphore with initial count 0
         start taskB and TaskC (Higher priority than taskA, no
round-robin)
         print bFlag, cFlag (should both be 0)
         semaphore_flush
         print bFlag, cFlag (should both be 1)

 TaskB/C:
         obtain semaphore
         set flag (B or C as appropriate)
         suspend/delete self

Successful test would show message from both tasks B and C after the
message from task A.