[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: finding who call all __init functions



Hello Adrian

Il giorno mar, 07/07/2020 alle 12.30 +0200, John Paul Adrian Glaubitz
ha scritto:
> Hi Guiseppe!
> On 7/7/20 11:54 AM, Giuseppe Sacco wrote
[...]
> > I would like to start knowing what is called after the cpufreq. How
> > do I find it? I know that drivers/cpufreq/pmac32-cpufreq.c has an
> > __init marked function and it is not compiled as a module. I
> > understood that such marked function will be discarded once boot is
> > complete, but I suspect somewhere a part of the kernel load all
> > __init marked functions. Is this correct? Where is it?
> 
> Why aren't you bisecting the kernel using git so you find the actual
> commit that broke the build? This way you will find the problem much
> quicker.

This is a possibility, but I was unaware that the bisect works between
branches (5.4 and 5.6). And, each recompile from scratch last about 6-7 
hours, so I prefer to work on a single kernel version, adding printk
somewhere and rebuilding only what is changed.

> Also, I would suggest discussing this kernel problem on the Linux
> kernel mailing list for PowerPC as the people there are actually
> responsible for the code you are trying to debug [1].

Thank you, I will ask for help there now.

Bye,
Giuseppe


Reply to: