kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: Giovanni Mascellani <gio@debian.org>
To: kernelnewbies@kernelnewbies.org
Subject: Re: Are there global constructors in the Linux kernel?
Date: Wed, 9 Oct 2019 08:54:02 +0200	[thread overview]
Message-ID: <7a3fa451-1f72-5c09-1a61-9e46f2237c3f@debian.org> (raw)
In-Reply-To: <CABfRCzhQkSgZaMX8PrZ2a0qSd=ezG3uxv8EC5TO21K0r9gv_jA@mail.gmail.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 2099 bytes --]

Hi,

[sending again after having replied just to the OP by mistake, sorry!]

Il 09/10/19 05:44, CRISTIAN ANDRES VARGAS GONZALEZ ha scritto:
> The gcc compiler searches for this function to run my program, but
> before that happens, I can use the global constructors and write a code
> that runs before the main function, but in the case of writing a kernel,
> why do I need to run lines of code before the kernel is executed ?, I
> understand that when writing a kernel there is no main function and that
> it is disabled to indicate it to the compiler. In the Linux kernel are
> there global constructors? If so, what things are executed before
> starting the kernel?

I am not a Linux expert, but I think I know enough on this specific
topic to give at least a partial answer: the global constructors feature
depends on the initialization code in the C runtime environment, which
depends on the operating system. In the case of the kernel, there is not
another operating system around, so everything that must happen at
initialization time must be done by the kernel itself, including setting
up the stack, zeroing uninitialized data and calling whatever you want
to be called. There cannot be any automatic way to do these things,
because there is nobody except the kernel itself who can do that.

This book has a nice and rather detailed write-up on what happens when
Linux boots (at least on x86_64):

  https://0xax.gitbooks.io/linux-insides/

You will see that nothing is called "automatically" like for global
constructors: everything is called explicitly and at the right moment.
This is also necessary because early kernel initialization routines
cannot assume that the system is in a consistent state, since their job
is to bring it to be. Therefore you must control precisely what must
happen when.

Hope this helps!

Giovanni.
-- 
Giovanni Mascellani <g.mascellani@gmail.com>
Postdoc researcher - Université Libre de Bruxelles





-- 
Giovanni Mascellani <g.mascellani@gmail.com>
Postdoc researcher - Université Libre de Bruxelles


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2019-10-09  6:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-09  3:44 Are there global constructors in the Linux kernel? CRISTIAN ANDRES VARGAS GONZALEZ
2019-10-09  6:54 ` Giovanni Mascellani [this message]
2019-10-09  8:54 ` Konstantin Andreev

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=7a3fa451-1f72-5c09-1a61-9e46f2237c3f@debian.org \
    --to=gio@debian.org \
    --cc=kernelnewbies@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).