kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: cartercheng@gmail.com (Carter Cheng)
To: kernelnewbies@lists.kernelnewbies.org
Subject: function stack frames in the kernel
Date: Mon, 12 Nov 2018 01:03:28 +0800	[thread overview]
Message-ID: <CALS6=qWC-P24t-tgmxUNMesoYxqxLqK8Ef4-v=iLtYcmWTBwEw@mail.gmail.com> (raw)

Hello,

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?

Thanks,

Carter
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20181112/553f5c9a/attachment.html>

WARNING: multiple messages have this Message-ID (diff)
From: Carter Cheng <cartercheng@gmail.com>
To: kernelnewbies@kernelnewbies.org
Subject: function stack frames in the kernel
Date: Mon, 12 Nov 2018 01:03:28 +0800	[thread overview]
Message-ID: <CALS6=qWC-P24t-tgmxUNMesoYxqxLqK8Ef4-v=iLtYcmWTBwEw@mail.gmail.com> (raw)
Message-ID: <20181111170328.7BvdCX_hghHKiBbMFEZwJmBIqrjawnGa1E6yiiD8pl0@z> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 355 bytes --]

Hello,

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?

Thanks,

Carter

[-- Attachment #1.2: Type: text/html, Size: 449 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:[~2018-11-11 17:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-11 17:03 Carter Cheng [this message]
2018-11-11 17:03 ` function stack frames in the kernel Carter Cheng
2018-11-11 17:55 ` Augusto Mecking Caringi
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='CALS6=qWC-P24t-tgmxUNMesoYxqxLqK8Ef4-v=iLtYcmWTBwEw@mail.gmail.com' \
    --to=cartercheng@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 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).