Lines Matching refs:fault

314 The standard exception handler is used when a fault is triggered by a thread
316 thread raises a fault due to an unmapped virtual memory page, the thread cannot
318 fault that would trigger the standard exception handler while it is set to a
322 should be trusted not to fault at all.
332 timeout fault handler, a fault will not be raised and the thread will continue
337 not have a timeout fault handler, servers may, allowing single-threaded,
340 completing the request.  Timeout fault handlers can access server reply objects
345 available budget returned, another timeout fault will be generated if the
346 nested server also has a timeout fault handler.
361 A thread's actions may result in a fault. Faults are delivered to the
363 The fault type is specified in the message label and is one of:
368 (indicating no fault occurred and this is a normal IPC message).
371 thread. This means that to send a fault message the fault endpoint
373 case, a double fault happens (generally the thread is simply suspended).
377 Capability faults may occur in two places. Firstly, a capability fault
382 on which the fault occurred may be the capability being invoked or an
385 Secondly, a capability fault can occur when \apifunc{seL4\_Recv}{sel4_recv} or \apifunc{seL4\_NBRec…
389 Replying to the fault IPC will restart the faulting thread. The contents of the
399 In receive phase (1 if the fault happened during a receive system call, 0
411 This fault occurs when a thread executes a system call with a syscall
418 Replying to the fault IPC allows the thread to be restarted
432 Replying to the fault IPC allows the thread to be restarted
477 capable of generating a fault \textbf{only} on instruction execution. Currently this will be
484 capable of generating a fault \textbf{only} on data access. Currently this will be set only
491 capable of generating a fault on either type of access -- i.e, the register
511 \caption{\label{tbl:debug_exception_result}Debug fault message layout. The
512 register API-ID is not returned in the fault message from the kernel on
536 call to \texttt{seL4\_TCB\_ConfigureSingleStepping}, or a fault-reply with
544 \texttt{bp\_num} argument in a single-step debug fault reply.
547 instructions before delivering the single-step fault message. \texttt{Num\_instructions}
550 the fault-reply to a single-step debug fault.
561 \caption{\label{tbl:single_step_exception_result}Single-step fault message layout.}
565 \label{sec:timeout-fault}
568 timeout fault handler that is not a null capability.  They allow a timeout
571 time consumed since the last timeout fault occurred on this scheduling context,
574 Timeout exception handlers can reply to a temporal fault with the registers set
579     the scheduling context object that the thread was running on when the fault
585     Timeout fault outcome on 32-bit architectures.} \end{table}
588 \label{sec:vm-fault}
590 The thread caused a page fault. Replying to the fault IPC will restart
599 Address that caused the fault. & \ipcbloc{seL4\_VMFault\_SP} \\
600 …Instruction fault (1 if the fault was caused by an instruction fetch). & \ipcbloc{seL4\_VMFault\_P…
601 Fault status register (FSR). Contains information about the cause of the fault. Architecture depend…
664 Should the guest execution mode generate any kind of fault, or if a message arrives