Next up in Linux's bootup process might (if compiletime-enabled) be static-calls!
A wrapper grabs appropriate locks, checks its only called once, logs any errors, & registers callbacks to trigger this to be dynamically called.
After validating there's work to do the inner logic sorts the static-calls table (via a helper & callbacks) & iterates over each "site". For each site it sums the call's address, checks if its an init routine, checks if the key's changed, & calls CPU-specific code.
1/3?
It uses helper routines to sort those entries (with callbacks), get the site's address & key, & 2 of them (by checking ranges) to check if its an init routine.
If it is an init routine a helper finalizes the key & sets a bitflag.
If the key has changed it updates a local, ensures it knows the module, allocates a site-mod propagating any failures, (via a couple helpers) validates a bitflag & returns the other bits of the other bits of the `type` property, & populates a site-mod or 2 to hold it.