Mach messages: coalition_notification
Message catalog and dispatch · All subsystem ranges · Kernel entry map
osfmk/mach/coalition_notification.defs. Service/callback interface outside the ordinary kernel kobject table. Follow local sender/receiver evidence; external service bodies are not supplied by the declaration.
Registration evidence: mig_e.
Reading these entries
IDs are computed from the explicit preprocessing profiles in the catalog guide, counting both routines and skip slots. They are not discovered from a running kernel. Each entry retains all observed names/declaration locations; the displayed fields come from the first non-skipped profile. Alternative declarations can have different fields. simpleroutine is one-way at the MIG interface level.
An interface contract block quotes the adjacent local .defs comment with whitespace normalized. Mechanism paragraphs explain selected implementation decisions. Local body links and call names identify implementation evidence; syntactic call lists are reading aids, not a proof that every listed call executes on every path. Short complete implementation bodies are included where especially useful.
Complete routine and reserved-slot catalog
5300: coalition_notification
Interface contract:
This is likely to change with 15385886.
Mechanism: The local sender obtains the host coalition notification port, checks that it is usable, sends the coalition ID/flags and releases the send right. The RPC result is not propagated by this void helper; the external service decides what to do with the lifecycle notification. Local path.
Declarations: coalition_notification (server64, server32, client64, client32, libsyscall64, sender64, local64).
Fields after preprocessing (server64):
simpleroutine coalition_notification(
RequestPort coalition_port : mach_port_t;
in id : uint64_t;
in flags : uint32_t);
Implementation boundary: no same-symbol receiver body was resolved in the indexed local C/C++ implementation files. Local source occurrences to follow: osfmk/kern/coalition.c:561. These may be senders, wrappers or declarations; they do not establish a local receiver.