osfmk/man/bootstrap_completed.html

   1 <h2>bootstrap_completed</h2>
   2 <hr>
   3 <p>
   4 <strong>Server Interface</strong> - Inform bootstrap server that
   5 initialization is complete.
   6 <h3>SYNOPSIS</h3>
   7 <pre>
   8 <strong>kern_return_t   bootstrap_completed</strong>
   9                 <strong>(mach_port_t</strong>                     <var>bootstrap_port</var>,
  10                  <strong>task_t</strong>                                    <var>task</var><strong>);</strong>
  11 </pre>
  12 <h3>PARAMETERS</h3>
  13 <dl>
  14 <p>
  15 <dt> <var>bootstrap_port</var>
  16 <dd>
  17 The port representing the calling task's bootstrap server.
  18 <p>
  19 <dt> <var>task</var>
  20 <dd>
  21 This parameter represents the calling task.
  22 </dl>
  23 <h3>DESCRIPTION</h3>
  24 <p>
  25 This interface allows a given server task to inform the bootstrap
  26 server that it is fully initialized and ready to handle requests.
  27 Upon receiving such notification, the bootstrap server can initialize
  28 any additional servers that may require services provided by the
  29 previously initialized server.
  30 <p>
  31 Note the following:  not all servers that may be invoked by the bootstrap server
  32 send this message upon startup.  If the bootstrap server is told to
  33 wait for this message before spawning further servers (via setting a
  34 flag in the <strong>bootstrap.conf</strong> file) and the server just invoked never
  35 sends this message, the bootstrap server will wait forever.
  36 <h3>NOTES</h3>
  37 <p>
  38 Currently, this interface is used exclusively by the default
  39 pager server so that the bootstrap server can defer initializing the
  40 OS server until the default pager is in place.  (In small memory
  41 configurations, an OS server may not be able to initialize
  42 successfully unless the default pager is ready to handle paging
  43 requests.)
  44 <h3>RETURN VALUES</h3>
  45 <dl>
  46 <p>
  47 <dt> <strong>KERN_SUCCESS</strong>
  48 <dd>
  49 The bootstrap server has updated the calling server's state with
  50 respect to bootstrap completion.
  51 <p>
  52 <dt> <strong>KERN_INVALID_ARGUMENT</strong>
  53 <dd>
  54 The bootstrap server does not recognize the calling server (the task
  55 specified by the <var>task</var> parameter).
  56 </dl>
  57 <h3>RELATED INFORMATION</h3>
  58 <p>
  59 Functions: