Lines Matching refs:single
262 single-step faults.}
268 The kernel provides support for the use of hardware single-stepping of userspace
273 an instruction breakpoint, to use when setting up the single-stepping
276 register to provide single-stepping functionality. If the caller's hardware platform requires the
279 breakpoint to provide single-stepping, seL4 will return \texttt{false} in \texttt{bp\_was\_consumed} and
284 the caller has disabled single-stepping and released that register, via a subsequent
287 \textbf{disables single stepping}.
290 single-stepping functionality, seL4 will restrict the number of registers that
291 can be configured as single-steppers, to one at any given time. The register that
292 is currently configured (if any) for single-stepping will be the implicit
293 \texttt{bp\_num} argument in a single-step debug fault reply.
295 The kernel's single-stepping, also supports skipping a certain number of
296 instructions before delivering the single-step fault message. \texttt{Num\_instructions}
297 should be set to \texttt{1} when single-stepping, or any non-zero integer value to skip that many
298 instructions before resuming single-stepping. This skip-count can also be set in
299 the fault-reply to a single-step debug fault.
413 Linking means that an I/O port capability can only be used in a single \apifunc{seL4\_X86\_VCPU\_EnableIOPort}{x86_vcpu_enableioport}