Continuing my study of Linux's bootup sequence...
Next up is booting up an "RCU" collection. This may involve registering an IRQ handler, invoking a tiny testsuite (via wrappers) to ensure it works, & invokes the cb-list initializer (via a wrapper possibly invoking it a couple times) including its locks, callbacks, & linkedlists.
Or it retrieves a process ID, runs the testsuite, logs specs via a small suite of helpers, invokes helpers each choosing specs under different conditions, ...
1/?
... invokes a helper & more in turn to extensively populate multiple arrays (including their locks, wait queues, linkedlists, callback, & more), possibly logs whats in those arrays, possibly registers an IRQ handler, registers a hotplugging callback, validates only one CPU's running yet, inits (via a few suites of helpers) several more properties, loads in data about the active CPU, allocates a couple workqueues, finalizes some specs, carefully (via a helper) queues the work to run this RCU, ...