Klever

At the moment EMG respects initialization of modules independently on whether they are built as loadable modules or as a part of the kernel (indeed #6571 was implemented although I suggested a small improvement). Moreover, often it initializes the kernel itself when its parts are analyzed together with modules since the same API is used. Unfortunately this isn't correct sometimes.

First of all EMG assumes that there can be a single initialization function for a given module or a kernel part object file. For modules this assumption works but this isn't the case for kernel parts. For instance, drivers/cpufreq/cpufreq.c has 2 initialization functions init_cpufreq_transition_notifier_list and cpufreq_core_init.

The second issue is the order of initialization. As far as I understand EMG doesn't distinguish different kinds of initialization functions although they can be responsible for determining the call order. Although I didn't encounter any problems due to the incorrect initialization order, but they definitely happen if one will analyze together large chunks of the kernel code.