1 <h2>mach_port_allocate_subsystem
</h2>
4 <strong>Function
</strong> - Create a port right associated with the caller-specified subsystem.
7 <strong>kern_return_t mach_port_allocate_subsystem
</strong>
8 <strong>(ipc_space_t
</strong> <var>task
</var>,
9 <strong>subsystem_t
</strong> <var>subsys
</var>,
10 <strong>mach_port_name_t
</strong> <var>mach_port_name_t
</var><strong>);
</strong>
17 [in task send right] The task acquiring the port right.
19 <dt> <var>subsys
</var>
21 [in scalar] The port right naming the subsystem the newly created port
22 is to be associated with.
26 [out scalar] The task's name for the port right. This can be any name
31 The
<strong>mach_port_allocate_subsystem
</strong> function creates a new right
33 with the specifed subsystem (specified via the
<var>subsys
</var> parameter)
34 previously registered via a call to the
35 <strong>mach_subsystem_create
</strong> interface.
36 The new right's name is returned in the
<var>name
</var> parameter. The
37 association of this port with the subsystem is immutable for the
40 Any RPC targeted at the new port will cause the kernel glue-code
41 to locate the server function address and argument signature in the
45 This interface is machine word length specific because of the port
47 <h3>RETURN VALUES
</h3>
50 <dt> <strong>KERN_SUCCESS
</strong>
52 The right is allocated.
54 <dt> <strong>KERN_INVALID_TASK
</strong>
58 <dt> <strong>KERN_INVALID_TASK
</strong>
62 <dt> <strong>KERN_RESOURCE_SHORTAGE
</strong>
64 Couldn't allocate memory.
66 <dt> <strong>KERN_NO_SPACE
</strong>
68 No room in space for another right.
70 <h3>RELATED INFORMATION
</h3>
73 <a href=
"mach_subsystem_create.html"><strong>mach_subsystem_create
</strong></a>,
74 <a href=
"thread_activation_create.html"><strong>thread_activation_create
</strong></a>.