On Sun, 16 Mar 2008, Peter Teoh wrote:
> But I think I have found the answer:
>
> init/main.c: kernel_init():
>
> /*
> * Ok, we have completed the initial bootup, and
> * we're essentially up and running. Get rid of the
> * initmem segments and start the user-mode stuff..
> */
> init_post();
>
> And in init_post():
>
> /* This is a non __init function. Force it to be noinline otherwise gcc
> * makes it inline to init() and it becomes part of init.text section
> */
> static int noinline init_post(void)
> {
> free_initmem(); <--------
... snip ...
but that's releasing all the "init" marked content at boot time.
the same thing has to happen upon each module load. i still don't see
how that affects what happens at module load time.
i'm still convinced this has to be happening in kernel/module.c
somewhere, i just haven't looked closely enough to see where.
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
Have classroom, will lecture.
http://crashcourse.ca Waterloo, Ontario, CANADA
========================================================================
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ
