Changeset 380 for trunk/hal/generic

Timestamp:

Aug 14, 2017, 6:31:25 PM (7 years ago)

Author:

alain

Message:

Remove the generic kernel/kern/do_exception files to handle exceptions in HAL.
The HAL call only the vmm_handle_page_fault() function if required.

File:

• trunk/hal/generic/hal_exception.h (modified) (2 diffs)

trunk/hal/generic/hal_exception.h

@@ -32 +32 @@
 // ALMOS-MKH defines three classes of exceptions:
 //
-// - NON_FATAL : exceptions such as "page fault" or "FPU unusable" are non fatal.
-//   The calling thread resumes execution when the exception has been handled.
+// - NON_FATAL : exceptions such as "page unmapped" or "FPU unusable" can be non fatal.
+//   => The hal_do_exception() function call the generic vmm_handle_page_fault(),
+//      or the fpu_handle_exception() function, and the calling thread resumes execution
+//      when the exception has been handled.
 //
-// - USER_ERROR : these exceptions such a "illegal vaddr" or "illegal write access"
-//   are fatal. The calling thread process is killed, after an "error" message on the
-//   kernel terminal.
+// - USER_ERROR : exceptions such a "illegal vaddr" or "illegal write access" are fatal.
+//   => The hal_do_exception() function send a kill signal to the calling thread process,
+//      and displays an error message on TXT0.
 //
-// - KERNEL_PANIC : events such as "no memory" or "kernel mistakes" are considered
-//   abnormal events. The calling core goes to sleep, after a "panic" message
-//   on the kernel terminal.
+// - KERNEL_PANIC : "kernel mistakes" are abnormal events.
+//   => The hal_do_exception() function calls the generic panic() function, to display
+//      a message on TXT0, disable IRQs and call the hal_core_sleep() function.
 //
-// For all exceptions, the faulty core context has been saved in a registers
-// array stored in the user thread descriptor (core in user mode), and in the
-// kernel stack (core in kernel mode). 
+// For all exceptions, the faulty core context has been saved in a registers array
+// stored in the user thread descriptor (for a core in user mode), and in the
+// kernel stack (for a core in kernel mode). 
 //
 // Any architecture specific implementation must implement this API.
@@ -55 +57 @@
 
 /*****************************************************************************************
- * This function implements the ALMOS-MKH exception handler.
- * It is called by the hal_kentry function when an exception is detected
- * by the hardware for an user thread running on a given core.
+ * This function is called by the hal_kentry() function when an exception is detected by
+ * the hardware for a given thread running on a given core.
  *****************************************************************************************
  * @ this      : pointer on the faulty thread descriptor.
- * @ regs_tbl  : array containing the core registers values saved by hal_kentry.
+ * @ regs_tbl  : array containing the core registers values saved by hal_kentry().
  ****************************************************************************************/
 void hal_do_exception( struct thread_s * this, 
                        reg_t           * regs_tbl );
 
-/*****************************************************************************************
- * This function prints on the kernel terminal the saved context (core registers)
- * and the thread state of a faulty thread.
- *****************************************************************************************
- * @ this      : pointer on the faulty thread descriptor.
- * @ regs_tbl  : pointer on the array containing the core registers values.
- ****************************************************************************************/
-void hal_exception_dump( struct thread_s * this,
-                         reg_t           * regs_tbl );
-
 #endif  // _HAL_EXCEPTION_H_