Changeset 101 for trunk/kernel/kern/process.h

Timestamp:

Jun 29, 2017, 4:44:52 PM (6 years ago)

Author:

alain

Message:

euh...

File:

• trunk/kernel/kern/process.h (modified) (6 diffs)

trunk/kernel/kern/process.h

@@ -65 +65 @@
 typedef struct fd_array_s
 {
-        remote_spinlock_t lock;             /*! lock protecting fd_array[] change.              */
-    uint32_t          current;          /*! current number of open files                    */
-        xptr_t            array[CONFIG_PROCESS_FILE_MAX_NR];  
+        remote_spinlock_t lock;                               /*! lock protecting fd_array      */
+    uint32_t          current;                            /*! current number of open files  */
+        xptr_t            array[CONFIG_PROCESS_FILE_MAX_NR];  /*! xptr on open file descriptors */
 }
 fd_array_t;
@@ -136 +136 @@
 
 /*********************************************************************************************
- * This structure defines the minimal information required by the process_make_exec()
- * function to build a new reference process descriptor, and the associated main thread.
+ * This structure defines the information required by the process_make_exec() function
+ * to create a new reference process descriptor, and the associated main thread.
  ********************************************************************************************/
 
 typedef struct exec_info_s
 {
-    pid_t              pid;            /*! process identifier                               */
-    pid_t              ppid;           /*! parent process identifier                        */
-
-    xptr_t             fd_array_xp;    /*! extended pointer on parent process fd_array      */
-
-    xptr_t             vfs_root_xp;    /*! extended pointer on file system root             */
-    xptr_t             vfs_cwd_xp;     /*! extended pointer on current working directory    */
-    xptr_t             vfs_bin_xp;     /*! extended pointer on process .elf file            */
-
+    xptr_t             parent_xp;      /*! extended pointer on parent process descriptor    */
+
+    xptr_t             stdin_xp;       /*! extended pointer on stdin  pseudo-file           */
     char               path[CONFIG_VFS_MAX_PATH_LENGTH];   /*!  .elf file path              */
 
@@ -180 +174 @@
 void process_free( process_t * process );
 
-/*********************************************************************************************
- * This function initializes the kernel process_zero descriptor (global variable) from
- * informations found in the boot_info.
- ********************************************************************************************* 
- * @ info      : pointer on local boot_info_t structure.
- ********************************************************************************************/
-void process_zero_init( boot_info_t * info );
-
 /********************************************************************************************* 
  * This function allocates memory and initialises the "process_init" descriptor and the
- * associated thread descriptor from information found in the "process_zero" descriptor.
- ********************************************************************************************* 
- * Any error gives a kernel panic.
- ********************************************************************************************/
+ * associated "thread_init" descriptor. It should be called once at the end of the kernel
+ * initialisation procedure, by the kernel "process_zero".
+ * The "process_init" is the first user process, and all other user process will be forked 
+ * from this process. The code executed by "process_init" is stored in a .elf file, whose
+ * pathname is defined by the CONFIG_PROCESS_INIT_PATH argument. It use fork/exec syscalls 
+ * to create the "shell" user process, and various other user daemon processes.
+ * Practically, it build the exec_info structure, register the stdin / stdout / stderr 
+ * pseudo-file descriptors and the vfs_root and vfs_cwd in parent process_zero, and call
+ * the generic process_make_exec() function, that makes the real job.
+ ********************************************************************************************/ 
 void process_init_create();
 
@@ -202 +194 @@
  * It set the pid / ppid / ref_xp fields.
  * It registers this process descriptor in three lists:
- * - the children_list in the parent process descriptor.
+ * - the children_list in the parent reference process descriptor.
  * - the local_list, rooted in the reference cluster manager.
  * - the copies_list, rooted in the owner cluster manager.
@@ -209 +201 @@
  * @ process      : [in] pointer on process descriptor to initialize.
  * @ pid          : [in] process identifier defined by owner cluster.
- * @ ppid         : [in] parent process identifier.
+ * @ parent_xp    : [in] extended pointer on parent process.
  ********************************************************************************************/
 void process_reference_init( process_t * process,
                              pid_t       pid,
-                             pid_t       ppid );
+                             xptr_t      parent_xp );
 
 /********************************************************************************************* 
@@ -259 +251 @@
 
 /********************************************************************************************* 
- * This function builds a new reference process descriptor and associated main thread.
+ * This function allocates memory and initializes a new user process descriptor,
+ * and the associated main thread, from informationd found in the <exec_info> structure
+ * (defined in the process.h file), that must be build by the caller.
+ * The new process inherit from the parent process (i) the open file descriptors, (ii) the
+ * vfs_root and the vfs_cwd inodes.
+ * It access to the .elf file to get the size of the code and data segments, and initialize
+ * the vsegs list in the VMM.
  * It is executed in the local cluster, that becomes both "owner" and "reference".
- * The new process descriptor and the main_thread are initialised using only informations 
- * found in the local exec_info structure, that must be build by the caller.
  * - It can be called by the process_init_create() function to build the "init" process.
  * - It can be called directly by the sys_exec() function in case of local exec.