From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <kernelnewbies-bounces@kernelnewbies.org>
Received: from mail-lf1-x12f.google.com ([2a00:1450:4864:20::12f])
 by shelob.surriel.com with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128)
 (Exim 4.91) (envelope-from <cartercheng@gmail.com>)
 id 1gLu2t-0006bi-QE
 for kernelnewbies@kernelnewbies.org; Sun, 11 Nov 2018 13:01:15 -0500
Received: by mail-lf1-x12f.google.com with SMTP id e26so2824074lfc.2
 for <kernelnewbies@kernelnewbies.org>; Sun, 11 Nov 2018 10:01:14 -0800 (PST)
MIME-Version: 1.0
References: <CALS6=qWC-P24t-tgmxUNMesoYxqxLqK8Ef4-v=iLtYcmWTBwEw@mail.gmail.com>
 <CADFy_4HaGzY3Up279jP13RrJUn6cPuy7S5hk967N3_b57V+GhQ@mail.gmail.com>
In-Reply-To: <CADFy_4HaGzY3Up279jP13RrJUn6cPuy7S5hk967N3_b57V+GhQ@mail.gmail.com>
From: Carter Cheng <cartercheng@gmail.com>
Date: Mon, 12 Nov 2018 02:00:02 +0800
Message-ID:
 <CALS6=qWeafWvH+HZG=W3ojv8XabS=znXYzuoGYh67htnvQGnfw@mail.gmail.com>
Subject: Re: function stack frames in the kernel
To: augustocaringi@gmail.com
Cc: kernelnewbies@kernelnewbies.org
List-Id: Learn about the Linux kernel <kernelnewbies.kernelnewbies.org>
List-Unsubscribe: <https://lists.kernelnewbies.org/mailman/options/kernelnewbies>,
 <mailto:kernelnewbies-request@kernelnewbies.org?subject=unsubscribe>
List-Archive: <http://lists.kernelnewbies.org/pipermail/kernelnewbies/>
List-Post: <mailto:kernelnewbies@kernelnewbies.org>
List-Help: <mailto:kernelnewbies-request@kernelnewbies.org?subject=help>
List-Subscribe: <https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies>,
 <mailto:kernelnewbies-request@kernelnewbies.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============8108530418350851546=="
Errors-To: kernelnewbies-bounces@kernelnewbies.org
Message-ID: <20181111180002.cIuhwk-n_yzmsMQ5MEqcfodn-8w-hmtx6Jl-RTm6eDA@z>

--===============8108530418350851546==
Content-Type: multipart/alternative; boundary="0000000000002c4781057a675b57"

--0000000000002c4781057a675b57
Content-Type: text/plain; charset="UTF-8"

Thanks for the reply but the link doesn't quite answer the question. I am
wondering how the pointer is handled so that there is one per thread by the
compiler. I perhaps was under the perhaps mistaken impression that the
stack pointer frame pointer management inside the compiler makes certain
assumptions in user space- but i am unsure how this applies to kernel space.

On Mon, Nov 12, 2018 at 1:55 AM Augusto Mecking Caringi <
augustocaringi@gmail.com> wrote:

> 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
>

--0000000000002c4781057a675b57
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks for the reply but the link doesn&#39;t quite answer=
 the question. I am wondering how the pointer is handled so that there is o=
ne per thread by the compiler. I perhaps was under the perhaps mistaken imp=
ression that the stack pointer frame pointer management inside the compiler=
 makes certain assumptions in user space- but i am unsure how this applies =
to kernel space.</div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Mo=
n, Nov 12, 2018 at 1:55 AM Augusto Mecking Caringi &lt;<a href=3D"mailto:au=
gustocaringi@gmail.com">augustocaringi@gmail.com</a>&gt; wrote:<br></div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex">On Sun, Nov 11, 2018 at 6:04 PM Carter Cheng &=
lt;<a href=3D"mailto:cartercheng@gmail.com" target=3D"_blank">cartercheng@g=
mail.com</a>&gt; wrote:<br>
&gt; I am wondering how the compiler divines which stack to use for functio=
n 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 c=
alls handled manually inside kernel code or is there something special insi=
de the compiler for handling this?<br>
<br>
I think this link can answer your question...<br>
<br>
<a href=3D"https://stackoverflow.com/questions/12911841/kernel-stack-and-us=
er-space-stack" rel=3D"noreferrer" target=3D"_blank">https://stackoverflow.=
com/questions/12911841/kernel-stack-and-user-space-stack</a><br>
<br>
-- <br>
Augusto Mecking Caringi<br>
</blockquote></div>

--0000000000002c4781057a675b57--


--===============8108530418350851546==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============8108530418350851546==--