bootstrap_completed.html   [plain text]

<strong>Server Interface</strong> - Inform bootstrap server that
initialization is complete.
<strong>kern_return_t   bootstrap_completed</strong>
                <strong>(mach_port_t</strong>                     <var>bootstrap_port</var>,
                 <strong>task_t</strong>                                    <var>task</var><strong>);</strong>
<dt> <var>bootstrap_port</var> 
The port representing the calling task's bootstrap server.
<dt> <var>task</var> 
This parameter represents the calling task.
This interface allows a given server task to inform the bootstrap
server that it is fully initialized and ready to handle requests.
Upon receiving such notification, the bootstrap server can initialize
any additional servers that may require services provided by the
previously initialized server.
Note the following:  not all servers that may be invoked by the bootstrap server
send this message upon startup.  If the bootstrap server is told to
wait for this message before spawning further servers (via setting a
flag in the <strong>bootstrap.conf</strong> file) and the server just invoked never
sends this message, the bootstrap server will wait forever.
Currently, this interface is used exclusively by the default
pager server so that the bootstrap server can defer initializing the
OS server until the default pager is in place.  (In small memory
configurations, an OS server may not be able to initialize
successfully unless the default pager is ready to handle paging
<dt> <strong>KERN_SUCCESS</strong>
The bootstrap server has updated the calling server's state with
respect to bootstrap completion.
<dt> <strong>KERN_INVALID_ARGUMENT</strong>
The bootstrap server does not recognize the calling server (the task
specified by the <var>task</var> parameter).