Changeset 36b86d7 in rtems for cpukit/sapi


Ignore:
Timestamp:
Jan 25, 2016, 7:55:52 PM (4 years ago)
Author:
Sebastian Huber <sebastian.huber@…>
Branches:
master
Children:
a853c851
Parents:
17e6f86
git-author:
Sebastian Huber <sebastian.huber@…> (01/25/16 19:55:52)
git-committer:
Sebastian Huber <sebastian.huber@…> (02/03/16 09:00:51)
Message:

score: Create idle threads via linker set

This allows a more fine grained rtems_initialize_data_structures().

Update #2408.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • cpukit/sapi/src/exinit.c

    r17e6f86 r36b86d7  
    143143
    144144  _POSIX_API_Initialize();
    145 
    146   _System_state_Set( SYSTEM_STATE_BEFORE_MULTITASKING );
    147 
    148   /*
    149    *  No threads should be created before this point!!!
    150    *  _Thread_Executing and _Thread_Heir are not set.
    151    *
    152    *  At this point all API extensions are in place.  After the call to
    153    *  _Thread_Create_idle() _Thread_Executing and _Thread_Heir will be set.
    154    */
    155   _Thread_Create_idle();
    156 
    157   /*
    158    *  Scheduling can properly occur now as long as we avoid dispatching.
    159    */
    160145}
    161146
     
    259244  rtems_initialize_data_structures,
    260245  RTEMS_SYSINIT_DATA_STRUCTURES,
     246  RTEMS_SYSINIT_ORDER_MIDDLE
     247);
     248
     249/*
     250 *  No threads should be created before this point!!!
     251 *  _Thread_Executing and _Thread_Heir are not set.
     252 *
     253 *  At this point all API extensions are in place.  After the call to
     254 *  _Thread_Create_idle() _Thread_Executing and _Thread_Heir will be set.
     255 *
     256 *  Scheduling can properly occur afterwards as long as we avoid dispatching.
     257 */
     258RTEMS_SYSINIT_ITEM(
     259  _Thread_Create_idle,
     260  RTEMS_SYSINIT_IDLE_THREADS,
    261261  RTEMS_SYSINIT_ORDER_MIDDLE
    262262);
Note: See TracChangeset for help on using the changeset viewer.