xnu-2422.1.72.tar.gz

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

diff --git a/osfmk/man/task_set_emulation_vector.html b/osfmk/man/task_set_emulation_vector.html
old mode 100755 (executable)
new mode 100644 (file)
index f496042..8296016
--- a/osfmk/man/task_set_emulation_vector.html
+++ b/osfmk/man/task_set_emulation_vector.html
@@ -1 +1,61 @@
-<h2>task_set_emulation_vector</h2>\r<hr>\r<p>\r<strong>Function</strong> - Establish the target task's user-level system call handlers. \r<h3>SYNOPSIS</h3>\r<pre>\r<strong>kern_return_t   task_set_emulation_vector</strong>\r                <strong>(task_t</strong>                                    <var>task</var>,\r                 <strong>int</strong>                               <var>vector_start</var>,\r                 <strong>emulation_vector_t</strong>            <var>emulation_vector</var>,\r                 <strong>mach_msg_type_number_t</strong>  <var>emulation_vector_count</var><strong>);</strong>\r</pre>\r<h3>PARAMETERS</h3>\r<dl>\r<p>\r<dt> <var>task</var> \r<dd>\r[in task send right]\rThe port for the task for which to establish the\rsystem call handler.\r<p>\r<dt> <var>vector_start</var> \r<dd>\r[in scalar]\rThe syscall number corresponding to the first element of\r<var>emulation_vector</var>.\r<p>\r<dt> <var>emulation_vector</var> \r<dd>\r[pointer to in array of <strong>vm_address_t</strong>]\rAn array of routine entrypoints \rfor the system calls starting with syscall number <var>vector_start</var>.\r<p>\r<dt> <var>emulation_vector_count</var> \r<dd>\r[in scalar]\rThe number of elements in <var>emulation_vector</var>.\r</dl>\r<h3>DESCRIPTION</h3>\r<p>\rThe <strong>task_set_emulation_vector</strong> function establishes\ra handler within the task \rfor a set of system calls.  When a thread executes a system call\rwith one of these \rnumbers, the system call will be redirected to the corresponding\rroutine within \rthe task's address space.\r<p>\rThese emulation handler addresses are inherited by child processes.\r<h3>NOTES</h3>\r<p>\rThis interface is machine word length specific because of the\rvirtual addresses \rin the <var>emulation_vector</var> parameter.\r<h3>RETURN VALUES</h3>\r<p>\rOnly generic errors apply.\r<h3>RELATED INFORMATION</h3>\r<p>\rFunctions:\r<a href="task_get_emulation_vector.html"><strong>task_get_emulation_vector</strong></a>.\r
\ No newline at end of file
+<h2>task_set_emulation_vector</h2>
+<hr>
+<p>
+<strong>Function</strong> - Establish the target task's user-level system call handlers. 
+<h3>SYNOPSIS</h3>
+<pre>
+<strong>kern_return_t   task_set_emulation_vector</strong>
+                <strong>(task_t</strong>                                    <var>task</var>,
+                 <strong>int</strong>                               <var>vector_start</var>,
+                 <strong>emulation_vector_t</strong>            <var>emulation_vector</var>,
+                 <strong>mach_msg_type_number_t</strong>  <var>emulation_vector_count</var><strong>);</strong>
+</pre>
+<h3>PARAMETERS</h3>
+<dl>
+<p>
+<dt> <var>task</var> 
+<dd>
+[in task send right]
+The port for the task for which to establish the
+system call handler.
+<p>
+<dt> <var>vector_start</var> 
+<dd>
+[in scalar]
+The syscall number corresponding to the first element of
+<var>emulation_vector</var>.
+<p>
+<dt> <var>emulation_vector</var> 
+<dd>
+[pointer to in array of <strong>vm_address_t</strong>]
+An array of routine entrypoints 
+for the system calls starting with syscall number <var>vector_start</var>.
+<p>
+<dt> <var>emulation_vector_count</var> 
+<dd>
+[in scalar]
+The number of elements in <var>emulation_vector</var>.
+</dl>
+<h3>DESCRIPTION</h3>
+<p>
+The <strong>task_set_emulation_vector</strong> function establishes
+a handler within the task 
+for a set of system calls.  When a thread executes a system call
+with one of these 
+numbers, the system call will be redirected to the corresponding
+routine within 
+the task's address space.
+<p>
+These emulation handler addresses are inherited by child processes.
+<h3>NOTES</h3>
+<p>
+This interface is machine word length specific because of the
+virtual addresses 
+in the <var>emulation_vector</var> parameter.
+<h3>RETURN VALUES</h3>
+<p>
+Only generic errors apply.
+<h3>RELATED INFORMATION</h3>
+<p>
+Functions:
+<a href="task_get_emulation_vector.html"><strong>task_get_emulation_vector</strong></a>.