Lines Matching refs:memory
36 \item[\obj{dataspace}] is an object that represents a dataspace. The dataspace itself may represent anything that may be modeled as a series of bytes including devices, RAM and files. If something has access to a dataspace object, it may read from the dataspace object, write to the dataspace object and execute the dataspace object by mapping a memory window to the dataspace, closing the dataspace, or deleting the dataspace. Performing these operations is dependent on the dataspace permissions.
38 \item[\obj{memwindow}] is an object that represents an address space range (i.e. a memory window) segment in a process's virtual memory. If something has access to a memory window object, it may perform operations on the memory window object such as mapping the memory window to a dataspace and mapping a frame into the memory window.
51 The process server interface provides the abstraction for managing processes and threads. The abstraction includes management of processes' virtual memory, memory window creation and deletion, process creation and deletion, death notification of client processes and thread management. Note that in implementations \cp{procserv}{session} could be the same capability as \cp{procserv}{process} in which case the process server is connectionless. \cp{procserv}{session} may also be shared with \cp{procserv}{anon} for simplification.
70 Create a new memory window segment for the calling client. Note that clients may only create memory windows for their own address space and alignment restrictions may apply here due to implementation and/or hardware restrictions. In the \refOS client environment, a valid memory window segment must be covering any virtual address ranges before any mapping can be performed (including dataspace and device frame mappings).
73 \item [size] The size of the memory window
80 Resize a memory window segment. This is an optional feature, which may be useful for implementing dynamic heap memory allocation on clients.
82 \item [size] The size of the memory window to resize to
87 Delete a memory window segment.
98 Unregister to stop being the pager for a client process's memory window
160 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.
189 \item [procserv\_window\_C] Capability to the memory window to unmap the dataspace from
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.
227 \item The dataspace is not revocable, so the receiving process does not need to protect itself from an untrusted fault handler on that memory
284 The process server is the most trusted component in the system. It runs as the initial kernel thread and does not depend on any other component (this avoids deadlock). The process server implementation is single-threaded. The process server also implements the dataspace interface for anonymous memory and acts as the memory manager.
288 \item Process server interface (naming, memory windows, processes and so on)
289 \item Dataspace server interface (for anonymous memory)