[apple/xnu.git] / osfmk / man / memory_object_data_unlock.html

<h2>memory_object_data_unlock</h2>\r<hr>\r<p>\r<strong>Server Interface</strong> - Request that the memory manager change current access permission on the specified memory object's data.\r<h3>SYNOPSIS</h3>\r<pre>\r<strong>kern_return_t   memory_object_data_unlock</strong>\r                <strong>(memory_object_t</strong>                  <var>memory_object</var>,\r                 <strong>memory_object_control_t</strong>         <var>memory_control</var>,\r                 <strong>vm_offset_t</strong>                             <var>offset</var>,\r                 <strong>vm_size_t</strong>                               <var>length</var>,\r                 <strong>vm_prot_t</strong>                       <var>desired_access</var><strong>);</strong>\r\r\r<strong>kern_return_t   seqnos_memory_object_data_unlock</strong>\r                <strong>(memory_object_t</strong>                  <var>memory_object</var>,\r                 <strong>mach_port_seqno_t</strong>                        <var>seqno</var>,\r                 <strong>memory_object_control_t</strong>         <var>memory_control</var>,\r                 <strong>vm_offset_t</strong>                             <var>offset</var>,\r                 <strong>vm_size_t</strong>                               <var>length</var>,\r                 <strong>vm_prot_t</strong>                       <var>desired_access</var><strong>);</strong>\r</pre>\r<h3>PARAMETERS</h3>\r<dl>\r<p>\r<dt> <var>memory_object</var> \r<dd>\r[in abstract-memory-object (receive) right]\rThe abstract memory\robject port that represents the memory object data.\r<p>\r<dt> <var>seqno</var> \r<dd>\r[in scalar]\rThe sequence number of this message relative to the abstract \rmemory object port.\r<p>\r<dt> <var>memory_control</var> \r<dd>\r[in memory-cache-control send right]\rThe memory cache control port \rto be used for a response by the memory manager.  If the memory\robject has been supplied to more than one kernel, this parameter\ridentifies the kernel that is making the call.\r<p>\r<dt> <var>offset</var> \r<dd>\r[in scalar]\rThe offset within the memory object.\r<p>\r<dt> <var>length</var> \r<dd>\r[in scalar]\rThe number of bytes to which the access applies, starting at \r<var>offset</var>.  The number converts to an integral number of memory object \rpages.\r<p>\r<dt> <var>desired_access</var> \r<dd>\r[in scalar]\rThe memory access modes requested for the cached data. \rPossible values are obtained by or'ing together the following values:\r<dl>\r<p>\r<dt> <strong>VM_PROT_READ</strong>\r<dd>\rAllows read access.\r<p>\r<dt> <strong>VM_PROT_WRITE</strong>\r<dd>\rAllows write access.\r<p>\r<dt> <strong>VM_PROT_EXECUTE</strong>\r<dd>\rAllows execute access.\r</dl>\r</dl>\r<h3>DESCRIPTION</h3>\r<p>\rA <strong>memory_object_data_unlock</strong> function is called as the\rresult of a kernel\rmessage requesting the memory manager to permit at least the\rdesired access to the \rspecified data cached by the kernel.  The memory manager is expected\rto use the \r<strong>memory_object_lock_request</strong> call in response.\r<h3>RETURN VALUES</h3>\r<p>\rOnly generic errors apply.\r<h3>RELATED INFORMATION</h3>\r<p>\rFunctions:\r<a href="MO_lock_completed.html"><strong>memory_object_lock_completed</strong></a>,\r<a href="memory_object_lock_request.html"><strong>memory_object_lock_request</strong></a>,\r<a href="memory_object_server.html"><strong>memory_object_server</strong></a>,\r<a href="SMO_server.html"><strong>seqnos_memory_object_server</strong></a>.\r