From: Augusto Mecking Caringi <augustocaringi@gmail.com>
To: cartercheng@gmail.com
Cc: kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: function stack frames in the kernel
Date: Sun, 11 Nov 2018 18:55:10 +0100 [thread overview]
Message-ID: <CADFy_4HaGzY3Up279jP13RrJUn6cPuy7S5hk967N3_b57V+GhQ@mail.gmail.com> (raw)
Message-ID: <20181111175510._ERv92hFfSn_yf_Kbj0S0g25Ua2REBdaflhd9UTvzt0@z> (raw)
In-Reply-To: <CALS6=qWC-P24t-tgmxUNMesoYxqxLqK8Ef4-v=iLtYcmWTBwEw@mail.gmail.com>
On Sun, Nov 11, 2018 at 6:04 PM Carter Cheng <cartercheng@gmail.com> wrote:
> I am wondering how the compiler divines which stack to use for function calls and placement of locals and arguments when a function call is made inside the kernel since the kernel has multiple call stacks. Are function calls handled manually inside kernel code or is there something special inside the compiler for handling this?
I think this link can answer your question...
https://stackoverflow.com/questions/12911841/kernel-stack-and-user-space-stack
--
Augusto Mecking Caringi
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2018-11-11 17:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-11 17:03 function stack frames in the kernel Carter Cheng
2018-11-11 17:03 ` Carter Cheng
2018-11-11 17:55 ` Augusto Mecking Caringi [this message]
2018-11-11 17:55 ` Augusto Mecking Caringi
2018-11-11 18:00 ` Carter Cheng
2018-11-11 18:00 ` Carter Cheng
2018-11-12 7:09 ` valdis.kletnieks at vt.edu
2018-11-12 7:09 ` valdis.kletnieks
2018-11-12 16:43 ` Carter Cheng
2018-11-12 16:43 ` Carter Cheng
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=CADFy_4HaGzY3Up279jP13RrJUn6cPuy7S5hk967N3_b57V+GhQ@mail.gmail.com \
--to=augustocaringi@gmail.com \
--cc=cartercheng@gmail.com \
--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).