Changes between Version 107 and Version 108 of library_stdio

Timestamp:

Sep 15, 2015, 12:38:15 PM (9 years ago)

Author:

alain

Comment:

--

library_stdio

@@ -49 +49 @@
  === 2) void '''giet_pthread_exit'''( void* string ) ===
 This function desactivates the calling thread. 
-The 'string' argument is a (user defined) log message displayed on the kernel TTY.
-No error possible.
+The 'string' argument is a (user defined) log message displayed on the kernel TTY0.
 
  === 3) int '''giet_pthread_join'''( pthread_t  trdid , void** ptr ) ===
@@ -63 +62 @@
 
  === 4) int '''giet_pthread_kill'''( pthread_id trdid , int signal ) === 
-This function deactivates the thread identified by the ''trdid'' argument when the ''signal'' argument is non zero.
-If the ''signal'' argument is zero, the thread existence is checked, but it is not deactivated.
+This function send a KILL signal to the thread identified by the ''trdid'' argument when the ''signal'' argument is non zero,
+and the thread will be deactivated at the next context switch.
+If the ''signal'' argument is zero, the thread existence is checked, but the KILL signal it is not sent.
  * trdid : unique thread identifier in vspace.
  * signal : deactivation if non zero.
@@ -72 +72 @@
  === 5) void '''giet_pthreadt_yield'''() ===
 The thread calling this function is descheduled and the processor is allocated to another thread.
-No error possible.
 
  === 6) void '''giet_pthread_assert'''( unsigned int condition, char* string ) ===
@@ -78 +77 @@
  * condition : thread exit if condition value is 0.
  * string : message displayed on TTY0.
-No error possible.
-
 
 
@@ -86 +83 @@
  === 1) void '''giet_kill_application'''( char* name ) ===
 This function kill the application identified by the vspace '''name''' argument: 
-All tasks are de-activated, the private peripherals or coprocessors are released, but the physical memory
-allocated to the killed application is not released.
+All application threads defined in the mapping receive a KILL signal and will be deactivated at the next context switch. The private peripherals or coprocessors are released. The physical memory allocated to the killed application segments is not released.
 
  === 2) void '''giet_exec_application'''( char* name ) ===
-This function starts execution for the the application identified by the vspace '''name''' argument: 
-The application code and data segment are loaded into memory from the .elf file. 
-All tasks contexts are initialized, and the tasks are activated.
+This function starts execution for the the application identified by the vspace '''name''' argument.
+The application  data segments are (re)loaded into memory from the .elf file. 
+Only thread that has the ''is_main'' flag set  in the mapping is activated.