Searched refs:exception (Results 1 - 8 of 8) sorted by relevance
/seL4-mcs-10.1.1/include/api/ |
H A D | failures.h | 20 enum exception { enum
|
/seL4-mcs-10.1.1/src/arch/x86/32/ |
H A D | traps.S | 333 # determine if we have a kernel exception 349 cmpl $0x20, %ecx # if interrupt vector is below 0x20, we have an exception 377 # Handle a kernel exception 382 * this might be a kernel exception that is the result of EFLAGS.TF being 386 * into the kernel, and so causes a debug-exception in kernel code, since 390 * exception continue. The debug exception handler will notice that it was 391 * kernel exception, and handle it appropriately -- that really just means 400 /* Else it was EFLAGS.TF that caused the kernel exception on SYSENTER. 404 * It will then be the debug exception handle [all...] |
/seL4-mcs-10.1.1/src/arch/riscv/ |
H A D | traps.S | 81 /* Save exception PC */ 96 li s4, 8 /* priv 1.10 has value 8 for ecall exception */ 97 bne s0, s4, exception 108 exception: label
|
/seL4-mcs-10.1.1/src/arch/x86/64/ |
H A D | traps.S | 18 * The exception in 64-bit mode: 125 /* Kernel exception handler if interrupt vector < 32. */ 133 /* Kernel exception handler if interrupt vector >= 32. 505 * this might be a kernel exception that is the result of EFLAGS.TF being 509 * into the kernel, and so causes a debug-exception in kernel code, since 513 * exception continue. The debug exception handler will notice that it was 514 * kernel exception, and handle it appropriately -- that really just means 524 /* Else it was EFLAGS.TF that caused the kernel exception on SYSENTER. 528 * It will then be the debug exception handle [all...] |
/seL4-mcs-10.1.1/manual/parts/ |
H A D | threads.tex | 256 Each thread has two associated exception-handler endpoints, a \emph{standard} 257 exception handler and a \emph{timeout} exception handler. If the thread causes 258 an exception, the kernel creates an IPC message with the relevant details and 260 Fault IPC messages are described in \autoref{sec:faults}. Standard exception-handler 262 \apifunc{seL4\_TCB\_SetSchedParams}{tcb_setschedparams} methods while Timeout exception 265 capability address for the exception handler can be associated with a thread. 268 an exception handler, a null capability can be used, however the consequences 269 are different per exeception handler type. Before raising an exception the 273 The exception endpoin [all...] |
H A D | io.tex | 142 \obj{VSpace} page faults are redirected to the thread's exception handler (see \autoref{sec:faults}), 145 There is no concept of an exception handler for an \obj{IOSpace}. Instead, faulting
|
H A D | cspace.tex | 224 exception to this scheme for \obj{Endpoint} and \obj{Notification} capabilities --- they support an 464 to either the calling thread or the thread's exception handler in its
|
H A D | vspace.tex | 342 Page faults are reported to the exception handler of the executed thread.
|
Completed in 42 milliseconds