manual/parts/ipc.tex

21 capabilities.
32 tag consists of four fields: the label, message length, number of capabilities
34 message length and number of capabilities determine either the number of
35 message registers and capabilities that the sending thread wishes to transfer,
36 or the number of message registers and capabilities that were actually
41 manner in which capabilities were received. It is described in
59         endpoint capabilities received}
100 of data and capabilities (namely the IPC buffer) to be transferred between two
124 Endpoint capabilities may be \emph{minted} to
133 capabilities with badges cannot be unbadged, rebadged or used to create
134 child capabilities with different badges.
143 Messages may contain capabilities, which will be copied to the
146 capabilities using an endpoint capability without the Grant right will
151 as a CPTR in the sending thread's capability space. The number of capabilities
161 sending thread may include multiple capabilities in the message. Messages
164 capabilities in the message can be \emph{unwrapped}.
187 phase or in the receive phase. In the send phase, all capabilities that
194 In the receive phase, seL4 transfers capabilities in the order that they
201     of the source capabilities is checked when the sending thread
213     capabilities until an attempt to save a capability to the
221 prematurely. The capabilities processed before the failure are still
223 buffer is set to the number of capabilities transferred up to failure.
269 is a non-owning reference, contrary to all the other capabilities. That means that