Searched refs:transfer (Results 1 - 8 of 8) sorted by relevance

/seL4-refos-master/kernel/include/api/
H A Dtypes.h57 cap_transfer_t transfer; local
59 transfer.ctReceiveRoot = (cptr_t)wptr[0];
60 transfer.ctReceiveIndex = (cptr_t)wptr[1];
61 transfer.ctReceiveDepth = wptr[2];
62 return transfer;
/seL4-refos-master/kernel/manual/parts/
H A Dipc.tex35 message registers and capabilities that the sending thread wishes to transfer,
42 \autoref{sec:cap-transfer}.
57 \ipcparam{seL4\_CPtr[]}{(in)}{caps}{Capabilities to transfer}
79 kernel uses as many physical registers as possible to transfer IPC
82 \texttt{msg} field to transfer arguments. However, it leaves room in
84 transfer or kernel object invocation required
141 \label{sec:cap-transfer}
147 result in transfer of the raw message, without any capability transfer.
191 no IPC or capability transfer take
[all...]
H A Dcspace.tex36 \autoref{sec:cap-transfer}). Furthermore, new capabilities can be
H A Dthreads.tex32 cap transfer.
/seL4-refos-master/projects/refos/design/
H A Dintro.tex67 \refOS assumes the microkernel that it runs on provides support for a capability-based access model, and more importantly, the ability to transfer badged capabilities via interprocess communication.
H A Dprotocol.tex196 \autoref{f:sharedata} is an example of how to set up a shared dataspace. Note that it is assumed that the share is not revocable and that sharing is with an entity that is trusted. Therefore, given two clients, at least one of the clients must trust the other client. Mutual distrust is not supported yet because capability transfer to an untrusted entity requires more than a direct call.
/seL4-refos-master/projects/refos/impl/apps/nethack/src/nethack-3.4.3/doc/
H A DGuidebook.tex1770 command, they transfer to the reader the knowledge of a spell (and
/seL4-refos-master/apps/nethack/src/nethack-3.4.3/doc/
H A DGuidebook.tex1770 command, they transfer to the reader the knowledge of a spell (and

Completed in 104 milliseconds