Searched refs:contents (Results 1 - 20 of 20) sorted by relevance

/seL4-refos-master/kernel/manual/tools/
H A Dparse_doxygen_xml.py109 # recurse on the contents
111 for item in para.contents:
291 for item in para.contents:
406 for item in para.contents:
414 for num, item in zip(range(sys.maxsize), para.contents):
/seL4-refos-master/kernel/manual/
H A Dmanual.tex73 % Subsubsections it table of contents
/seL4-refos-master/projects/refos/design/
H A Dprotocol.tex283 \autoref{f:initdata} shows creating a dataspace and setting the dataspace so that it is initialised with the contents of another dataspace. This example initialises a RAM dataspace (with the process server acting as its data server as per \refOS's implementation) with the contents of an executable file from another dataspace.
321 \caption{Sample protocol for creating a dataspace initialised with the contents of another dataspace}
372 P abox C [ label = "Datamap ELF header file contents"];
405 A memory window should bookkeep its state, which vspace it belongs to, where and how long the memory segment is and the state of the memory window's contents. A memory window may be unmapped or mapped to a dataspace, and that dataspace may or may not be content initialised. In \refOS, the process server is the anonymous memory dataserver, so in \refOS the memory window data structure has extra bookkeeping information for the internal anonymous dataspace mapping state. Also, \refOS separates the memory window's size and offset into multiple windows.
H A Dinterface.tex160 Open a new dataspace at the dataspace server, which represents a series of bytes. Dataspace mapping methods such as datamap() and init\_data() directly or indirectly map the contents of a dataspace into a memory window after which the contents can be read from and written to. The concept of a dataspace in \refOS is similar to a file in UNIX: what a dataspace represents depends on the server that is implementing the interface.
181 \item [procserv\_window\_C] Capability to the memory window to map the dataspace contents into
187 Unmap the contents of the data from the given memory window.
194 Initialise a dataspace by the contents of a source dataspace. The source dataspace is where the content is, and the source dataspace must originate from the invoked dataserver. Whether the destination dataspace and the source dataspace can originate from the same dataserver depends on the dataserver implementation: one should refer to the dataserver documentation. One example use case for this is a memory manager implementing the dataspace for RAM having a block of RAM initialised by an external data source such as a file from a file server.
203 Call a remote dataspace server to have the remote dataspace server initalised by the contents of the local dataspace server. The local dataspace server must bookkeep the remote dataspace server's ID. The remote dataspace server then will request from the given endpoint content initialisation with the remote dataspace server providing its ID in the notification.
296 The file server is more trusted than clients, but it is less trusted than the process server (this avoids deadlock). In \refOS, the file server does not use a disk driver and the actual file contents are compiled into the file server executable itself using a cpio archive. The file server acts as the main data server in \refOS.
H A Dintro.tex15 The overall design of \refOS revolves around the abstraction of a dataspace. A dataspace is a memory space (a series of bytes) representing anything from physical RAM to file contents on a disk to a device or even to a random number generator. The concept is analogous to UNIX files which may represent anything from \texttt{/usr/bin/sh} to \texttt{/dev/audio} to \texttt{/dev/urandom}.
158 Note that \refOS does not make the assumption that the kernel is able to pass message contents via the notification itself, just that the kernel is able to pass just the notification. In order for the actual message to be delivered along with the notification, the implementation of the protocol may for instance make use of a shared buffer.
/seL4-refos-master/projects/refos/impl/apps/nethack/src/nethack-3.4.3/src/
H A Ddo.c604 struct obj *contents; local
605 for(contents=obj->cobj; contents; contents=contents->nobj)
606 obj_no_longer_held(contents);
H A Dmkobj.c809 struct obj *contents; local
816 for(contents=obj->cobj; contents; contents=contents->nobj)
817 cwt += weight(contents);
820 * of the bag plus the weight of the bag's contents modified
823 * Bag status Weight of contents
H A Dobjnam.c1764 int halfeaten, mntmp, contents; local
1799 contents = UNDEFINED;
1893 contents = EMPTY;
1971 contents = SPINACH;
2239 contents = SPINACH;
2509 case TIN: if (contents==EMPTY) {
2512 } else if (contents==SPINACH) {
/seL4-refos-master/apps/nethack/src/nethack-3.4.3/src/
H A Ddo.c604 struct obj *contents; local
605 for(contents=obj->cobj; contents; contents=contents->nobj)
606 obj_no_longer_held(contents);
H A Dmkobj.c809 struct obj *contents; local
816 for(contents=obj->cobj; contents; contents=contents->nobj)
817 cwt += weight(contents);
820 * of the bag plus the weight of the bag's contents modified
823 * Bag status Weight of contents
H A Dobjnam.c1764 int halfeaten, mntmp, contents; local
1799 contents = UNDEFINED;
1893 contents = EMPTY;
1971 contents = SPINACH;
2239 contents = SPINACH;
2509 case TIN: if (contents==EMPTY) {
2512 } else if (contents==SPINACH) {
/seL4-refos-master/kernel/src/arch/x86/32/
H A Dtraps.S512 # Assume following register contents when called:
/seL4-refos-master/kernel/manual/parts/
H A Dbootup.tex71 bootstrapping. Their exact contents depend on the userland image size,
138 \texttt{seL4\_Word} & \texttt{id} & Identifier indicating the contents of the chunk \\
H A Dapi.tex80 \newcommand{\errorenumdesc}{A return value of \texttt{0} indicates success. A non-zero value indicates that an error occurred. See \autoref{sec:errors} for a description of the message register and tag contents upon error.}
H A Dthreads.tex299 types, the contents of the reply message may be used to set the values in the
346 The register contents are transferred via the IPC buffer.
379 Replying to the fault IPC will restart the faulting thread. The contents of the
581 the thread. The contents of the IPC message are given below.\\
H A Dipc.tex54 \ipcparam{seL4\_Word[]}{}{msg}{Message contents}
H A Dio.tex220 modify memory contents that it has been explicitly given access to and allow
/seL4-refos-master/kernel/src/arch/x86/64/
H A Dtraps.S40 * as if the segment base is zero. Mode change does not change the contents
49 * base, limit and attribute fields are all loaded. However, the contents
625 # Assume following register contents when called:
/seL4-refos-master/projects/refos/impl/apps/nethack/src/nethack-3.4.3/doc/
H A DGuidebook.tex2577 Sort the pack contents by type when displaying inventory (default on).
/seL4-refos-master/apps/nethack/src/nethack-3.4.3/doc/
H A DGuidebook.tex2577 Sort the pack contents by type when displaying inventory (default on).

Completed in 158 milliseconds