From: tobias@gambas-buch.de (Tobias Boege)
To: kernelnewbies@lists.kernelnewbies.org
Subject: do_initcalls
Date: Sun, 17 Mar 2013 16:11:54 +0100 [thread overview]
Message-ID: <20130317151154.GC1280@aurora> (raw)
In-Reply-To: <20130317144118.GA3086@debian.localdomain>
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.
Regards,
Tobi
next prev parent reply other threads:[~2013-03-17 15:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-17 14:41 do_initcalls ishare
2013-03-17 15:11 ` Tobias Boege [this message]
2013-03-18 1:10 ` do_initcalls ishare
2013-03-18 16:35 ` do_initcalls Tobias Boege
2013-03-19 1:31 ` do_initcalls ishare
2013-03-19 21:26 ` do_initcalls Tobias Boege
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=20130317151154.GC1280@aurora \
--to=tobias@gambas-buch.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).