manual/parts/threads.tex

114 A thread's actions may result in a fault. Faults are delivered to the
116 The fault type is specified in the message label and is one of:
118 or seL4\_Fault\_NullFault (indicating no fault occurred and this is a normal IPC message).
121 thread. This means that to send a fault message the fault endpoint
126 Capability faults may occur in two places. Firstly, a capability fault
131 on which the fault occurred may be the capability being invoked or an
134 Secondly, a capability fault can occur when \apifunc{seL4\_Recv}{sel4_recv} or \apifunc{seL4\_NBRecv}{sel4_nbrecv}
138 Replying to the fault IPC will restart the faulting thread. The contents of the
148 In receive phase (1 if the fault happened during a receive system call, 0
160 This fault occurs when a thread executes a system call with a syscall
167 Replying to the fault IPC allows the thread to be restarted
181 Replying to the fault IPC allows the thread to be restarted
226 capable of generating a fault \textbf{only} on instruction execution. Currently this will be
233 capable of generating a fault \textbf{only} on data access. Currently this will be set only
240 capable of generating a fault on either type of access -- i.e, the register
260 \caption{\label{tbl:debug_exception_result}Debug fault message layout. The
261 register API-ID is not returned in the fault message from the kernel on
285 call to \texttt{seL4\_TCB\_ConfigureSingleStepping}, or a fault-reply with
293 \texttt{bp\_num} argument in a single-step debug fault reply.
296 instructions before delivering the single-step fault message. \texttt{Num\_instructions}
299 the fault-reply to a single-step debug fault.
310 \caption{\label{tbl:single_step_exception_result}Single-step fault message layout.}
314 \label{sec:vm-fault}
316 The thread caused a page fault. Replying to the fault IPC will restart
325 Address that caused the fault. & \ipcbloc{seL4\_VMFault\_SP} \\
326     Instruction fault (1 if the fault was caused by an instruction fetch). & \ipcbloc{seL4\_VMFault\_PrefetchFault}  \\
327 Fault status register (FSR). Contains information about the cause of the fault. Architecture dependent. & \ipcbloc{seL4\_VMFault\_FSR} \\
390 Should the guest execution mode generate any kind of fault, or if a message arrives