Thread Control Block

The following is the declaration of the Thread Control Block.

struct tcb {
  u32_t status;
  struct reg_context thread_context;
  void *stack;
  struct thread_info thread_params;
  u32_t executedTime;
  struct tcb *recoveryTask;
  u32_t sched_field;
  u32_t magic_key;
};

 

  • unsigned int status

    This field holds the status information of the current thread. It can be one of THREAD_ON_CPU, THREAD_READY, THREAD_SUSPENDED THREAD_BLOCKED, THREAD_EXITED or THREAD_MISSED_DEADLINE. 

    This field is not directly updated by the kernel. The kernel thread library informs the scheduler about the status of a thread through the Scheduler API. It is upto the scheduler object to keep this field consistent. For example when a thread exits, the kernel calls the function set_mode(curr_thread,THREAD_EXITED) of the scheduler API. This approach of calling a scheduler function to update the status helps, when the sheduler needs to do additional work (apart from setting it's status) whenever the status of a thread changes. For example, for periodic threads, it might reset them when they exit. 

  • struct reg_context thread_context

    This structure stores the context of a thread. The structure reg_context is architecture specific. This field is accessed by the kernel thread library only. (The scheduler object should not mess with it).

  • struct thread_info thread_params

    This field holds the initial thread parameters, like the start function, stack size, deadline etc. This information is required for resetting threads.

  • void * stack

    This field is a pointer to the stack of the thread.

  • u32_t executedTime

    This field can be used for keeping profiling information for the thread. This is currently not being used.

  • u32_t sched_field

    This field is meant for use by the scheduler object. The kernel never accessed this field. 

    Typically this field will be used by the scheduler object for constructing datastructure of tcb's. For example if the scheduler object stores the ready threads in a list, this field would be used as next pointer.

  • u32_t magic_key

    This field is used for debugging and should go away in the final release.

http://www.cse.iitd.ernet.in/~soumyadeb/projects/mtp/report/node56.html

------------------越是喧嚣的世界，越需要宁静的思考------------------ 合抱之木，生于毫末；九层之台，起于垒土；千里之行，始于足下。 积土成山，风雨兴焉；积水成渊，蛟龙生焉；积善成德，而神明自得，圣心备焉。故不积跬步，无以至千里；不积小流，无以成江海。骐骥一跃，不能十步；驽马十驾，功在不舍。锲而舍之，朽木不折；锲而不舍，金石可镂。蚓无爪牙之利，筋骨之强，上食埃土，下饮黄泉，用心一也。蟹六跪而二螯，非蛇鳝之穴无可寄托者，用心躁也。