From: june.tune.sea@gmail.com (ishare)
To: kernelnewbies@lists.kernelnewbies.org
Subject: do_initcalls
Date: Tue, 19 Mar 2013 09:31:59 +0800 [thread overview]
Message-ID: <20130319013159.GA25595@debian.localdomain> (raw)
In-Reply-To: <20130318163529.GF728@aurora>
On Mon, Mar 18, 2013 at 05:35:29PM +0100, Tobias Boege wrote:
> On Mon, 18 Mar 2013, ishare wrote:
> > On Sun, Mar 17, 2013 at 04:11:54PM +0100, Tobias Boege wrote:
> > > On Sun, 17 Mar 2013, ishare wrote:
> > > >
> > > > for (call = &__initcall_start; call < &__initcall_end; call++)
> > > > (*call)();
> > > >
> > > > I want to know where are these function point assigned by specified function ?
> > > >
> > > > thanks!
> > >
> > > As per include/asm-generic/vmlinux.lds.h and your arch's vmlinux.lds.S (I
> > > actually only looked at x86's), the __initcall_{start,end} variables are the
> > > start and end of the __initcall ELF section which contains all the sub-level
> > > sections.
> > >
> > > Functions can be put into these sections when they are given to one
> > > of the *_initcall macros from include/linux/init.h.
> >
> > I have configure kernel supporting rom filesystem ,and register it by module_init(init_romfs_fs) ,
> > but why the function : init_romfs_fs not be called from (*call)() ?
> >
> > thanks!
> >
>
> This is strange - *unless* you build romfs as a module. Have again a look at
> the aforementioned include/linux/init.h. There's a fairly big comment on the
> procedure:
>
> /**
> * module_init() - driver initialization entry point
> * @x: function to be run at kernel boot time or module insertion
> *
> * module_init() will either be called during do_initcalls() (if
> * builtin) or at module insertion time (if a module). There can only
> * be one per module.
> */
Does this mean it chould not be called during do_initcalls if I config it as a module ?
If this ,how to change it to be builtin module?
what is called module insertion time? Is that time I explicitely call some insert function?
thanks!
>
> Regards,
> Tobi
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2013-03-19 1:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-17 14:41 do_initcalls ishare
2013-03-17 15:11 ` do_initcalls Tobias Boege
2013-03-18 1:10 ` do_initcalls ishare
2013-03-18 16:35 ` do_initcalls Tobias Boege
2013-03-19 1:31 ` ishare [this message]
2013-03-19 21:26 ` do_initcalls Tobias Boege
-- strict thread matches above, loose matches on Subject: below --
2005-11-25 7:41 do_initcalls Jaap de Jong
2005-11-29 6:27 ` do_initcalls Gil Madar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130319013159.GA25595@debian.localdomain \
--to=june.tune.sea@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.