Retype an untyped object Given a capability, , to an untyped object, creates of the requested type. Creates capabilities to the new objects starting at in the CNode specified by , , and . For variable-sized kernel objects, the argument is used to determine the size of objects to create. The relationship between and object size depends on the type of object being created. See for more information about object sizes. See for more information about how untyped memory is retyped. See for more information about the placement of capabilities to created objects. Read a thread's registers into the first fields of a given seL4_UserContext See Set a thread's registers to the first fields of a given seL4_UserContext See Copy the registers from one thread to another In the context of this function, frame registers are those that are read, modified or preserved by a system call and integer registers are those that are not. Refer to the seL4 userland library source for specifics. Set the parameters of a TCB See Change a thread's priority See Change a thread's maximum controlled priority See Change a thread's priority and maximum controlled priority. See Set a thread's IPC buffer See Sections and Set the fault endpoint, CSpace and VSpace of a thread See Suspend a thread See Resume a thread See Binds a notification object to a See Unbinds any notification object from a See Change a thread's current CPU in multicore machine See Set or modify a thread's breakpoints or watchpoints. Calls to this function overwrite previous configurations for the target breakpoint. Do not use this with seL4_SingleStep: the API will reject the call and return an error. Instead, use seL4_TCB_ConfigureSingleStepping to configure single-stepping. See Read a breakpoint or watchpoint's current configuration. See A : Struct that contains `', an seL4 API error value, `', the virtual address at which the breakpoint will currently be triggered; `', the type of operation which will currently trigger the breakpoint, whether instruction execution, or data access; `', integer value for the span-size of the breakpoint. Usually a power of two (1, 2, 4, etc.); `', the access direction that will currently trigger the breakpoint, whether read, write, or both and `', which indicates whether or not the breakpoint will currently be triggered if the match conditions are met. Disables a hardware breakpoint or watchpoint. The caller should assume that the underlying configuration of the hardware registers has also been cleared. Do not use this to clear single-stepping: the API will reject the call and return an error. Instead, use seL4_TCB_ConfigureSingleStepping to disable single-stepping. See Set or modify single stepping options for the target TCB. Subsequent calls to this function overwrite previous configuration. Depending on your processor architecture, this may or may not require the consumption of a hardware register. See Sections and A : Struct that contains `', an seL4 API error value, `', a boolean which indicates whether or not the breakpoint ID that was passed to the function, was consumed in the setup of the single-stepping functionality: if this is , the caller should not attempt to re-use until it has disabled the single-stepping functionality via a subsequent call to seL4_TCB_ConfigureSingleStepping with an argument of 0. Delete all child capabilities of a capability See . Delete a capability See . The cancel badged sends method is intend to allow for the reuse of badges by an authority. When used with a badged endpoint capability it will cancel any outstanding send operations for that endpoint and badge. This operation has no effect on un-badged or other objects. See . Copy a capability, setting its access rights whilst doing so See . The rights inherited by the new capability. Possible values for this type are given in . Copy a capability, setting its access rights and badge whilst doing so See . The rights inherited by the new capability. Possible values for this type are given in . Move a capability See . Move a capability, setting its badge in the process See . Given 3 capability slots - a destination, pivot and source - move the capability in the pivot slot to the destination slot and the capability in the source slot to the pivot slot See . Save the reply capability from the last time the thread was called in the given CSpace so that it can be invoked later See . Create an IRQ handler capability See . Acknowledge the receipt of an interrupt and re-enable it See . Set the notification which the kernel will signal on interrupts controlled by the supplied IRQ handler capability See . Clear the handler capability from the IRQ slot See . Change the domain of a thread. See .