Changeset 672 for trunk/kernel/mm/vmm.h

Timestamp:

Nov 19, 2020, 11:49:01 PM (4 years ago)

Author:

alain

Message:

1) Introduce up to 4 command lines arguments in the KSH "load" command.
These arguments are transfered to the user process through the
argc/argv mechanism, using the user space "args" vseg.

2) Introduce the named and anonymous "pipes", for inter-process communication
through the pipe() and mkfifo() syscalls.

3) Introduce the "chat" application to validate the two above mechanisms.

4) Improve printk() and assert() fonctions in printk.c.

File:

• trunk/kernel/mm/vmm.h (modified) (5 diffs)

trunk/kernel/mm/vmm.h

@@ -3 +3 @@
  *
  * Authors   Ghassan Almaless (2008,2009,2010,2011, 2012)
- *           Alain Greiner (2016,2017,2018,2019,2020))
+ *           Alain Greiner    (2016,2017,2018,2019,2020))
  *
  * Copyright (c) UPMC Sorbonne Universites
@@ -53 +53 @@
  *   corresponding bit in the bitmap.
  * - The de-allocator reset the corresponding bit in the bitmap.
+ *
+ * An  architecture dependant hal_vmm_display() function is defined in <hal_vmm.h> file.
  ********************************************************************************************/
 
@@ -93 +95 @@
 /*********************************************************************************************
  * This structure defines the Virtual Memory Manager for a given process in a given cluster.
- * This local VMM implements four main services:
- * 1) It contains the local copy of vseg list (VSL), only complete in referrence.
+ * This VMM implements four main services:
+ * 1) It contains the local copy of the vseg list (VSL), only complete in reference cluster.
  * 2) It contains the local copy of the generic page table (GPT), only complete in reference.
  * 3) The stack manager dynamically allocates virtual memory space for the STACK vsegs.
@@ -141 +143 @@
 
 /*********************************************************************************************
- * This function makes only a partial initialisation of the VMM attached to an user
- * process: It intializes the STACK and MMAP allocators, and the VSL lock.
- * - The GPT has been previously created, with the hal_gpt_create() function.
- * - The "kernel" vsegs are previously registered, by the hal_vmm_kernel_update() function.
- * - The "code" and "data" vsegs arlmmmmmme registered by the elf_load_process() function.
- * - The "stack" vsegs are dynamically registered by the thread_user_create() function.
+ * This function makes a partial initialisation of the VMM attached to an user process.
+ * It intializes the STACK and MMAP allocators, the VSL lock, and the instrumentation
+ * counters, but it does not register any vseg in the VSL:
+ * - The "kernel" vsegs are registered, by the hal_vmm_kernel_update() function.
+ * - The "args" & "envs" vsegs are registered by the process_make_exec() function.
+ * - The "code" and "data" vsegs are registered by the elf_load_process() function.
+ * - The "stack" vsegs are registered by process_make_exec() / thread_user_create().
  * - The "file", "anon", "remote" vsegs are dynamically registered by the mmap() syscall.
  *********************************************************************************************
@@ -155 +158 @@
 
 /*********************************************************************************************
- * This function re-initialises the VMM attached to an user process to prepare a new
- * call to the vmm_user_init() function after an exec() syscall.
- * It removes from the VMM of the process identified by the <process> argument all
- * all user vsegs, by calling the vmm_remove_vseg() function.
- * - the vsegs are removed from the VSL.
- * - the corresponding GPT entries are removed from the GPT.
- * - the physical pages are released to the relevant kmem when they are not shared.
- * The VSL and the GPT are not modified for the kernel vsegs.
+ * This function is called by the process_make_exec() function to re-initialises the VMM
+ * attached to an user process:
+ * - It removes from the VMM of the process identified by the <process> argument all user
+ *   vsegs, by calling the vmm_remove_vseg() function: the vsegs are removed from the VSL,
+ *   the corresponding GPT entries are removed from the GPT, and the physical pages are 
+ *   released to the relevant kmem when they are not shared.
+ * - The VSL and the GPT are not modified for the kernel vsegs.
+ * - Finally, it calls the vmm_user_init() function to re-initialize the STAK and MMAP
+ *   allocators, and the lock protecting GPT.
  *********************************************************************************************
  * @ process   : pointer on process descriptor.