Changeset 18269cef in rtems

Timestamp:

02/13/96 15:37:33 (28 years ago)

Author:

Joel Sherrill <joel.sherrill@…>

Branches:

4.10, 4.11, 4.8, 4.9, 5, master

Children:

b38955b

Parents:

a31ddf7

Message:

comment added to describe synchronization logic in timeout routine

Files:

• c/src/exec/rtems/src/event.c (modified) (3 diffs)
• cpukit/rtems/src/event.c (modified) (3 diffs)

c/src/exec/rtems/src/event.c

@@ -199 +199 @@
   switch ( sync_state ) {
     case EVENT_SYNC_SYNCHRONIZED:
+      /*
+       *  This cannot happen.  It indicates that this routine did not
+       *  enter the synchronization states above.
+       */
+      return;
+
     case EVENT_SYNC_NOTHING_HAPPENED:
       _ISR_Enable( level );
       return;
+
     case EVENT_SYNC_TIMEOUT:
       executing->Wait.return_code = RTEMS_TIMEOUT;
@@ -207 +214 @@
       _Thread_Unblock( executing );
       return;
+
     case EVENT_SYNC_SATISFIED:
       if ( _Watchdog_Is_active( &executing->Timer ) ) {
@@ -329 +337 @@
       break;
     case OBJECTS_LOCAL:
+ 
+      /*
+       *  If the event manager is not synchronized, then it is either
+       *  "nothing happened", "timeout", or "satisfied".   If the_thread
+       *  is the executing thread, then it is in the process of blocking
+       *  and it is the thread which is responsible for the synchronization 
+       *  process.
+       *
+       *  If it is not satisfied, then it is "nothing happened" and
+       *  this is the "timeout" transition.  After a request is satisfied,
+       *  a timeout is not allowed to occur.
+       */
+
       if ( _Event_Sync_state != EVENT_SYNC_SYNCHRONIZED && 
            _Thread_Is_executing( the_thread ) ) {

cpukit/rtems/src/event.c

@@ -199 +199 @@
   switch ( sync_state ) {
     case EVENT_SYNC_SYNCHRONIZED:
+      /*
+       *  This cannot happen.  It indicates that this routine did not
+       *  enter the synchronization states above.
+       */
+      return;
+
     case EVENT_SYNC_NOTHING_HAPPENED:
       _ISR_Enable( level );
       return;
+
     case EVENT_SYNC_TIMEOUT:
       executing->Wait.return_code = RTEMS_TIMEOUT;
@@ -207 +214 @@
       _Thread_Unblock( executing );
       return;
+
     case EVENT_SYNC_SATISFIED:
       if ( _Watchdog_Is_active( &executing->Timer ) ) {
@@ -329 +337 @@
       break;
     case OBJECTS_LOCAL:
+ 
+      /*
+       *  If the event manager is not synchronized, then it is either
+       *  "nothing happened", "timeout", or "satisfied".   If the_thread
+       *  is the executing thread, then it is in the process of blocking
+       *  and it is the thread which is responsible for the synchronization 
+       *  process.
+       *
+       *  If it is not satisfied, then it is "nothing happened" and
+       *  this is the "timeout" transition.  After a request is satisfied,
+       *  a timeout is not allowed to occur.
+       */
+
       if ( _Event_Sync_state != EVENT_SYNC_SYNCHRONIZED && 
            _Thread_Is_executing( the_thread ) ) {