Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: David Daney <ddaney@avtrex.com>
Cc: zhan rongkai <zhanrk@gmail.com>, linux-mips@linux-mips.org
Subject: Re: Why does MIPS/Linux always reserve 32 bytes in the top of each process's kernel stack space
Date: Sat, 29 Jan 2005 01:02:35 +0100	[thread overview]
Message-ID: <20050129000235.GA11602@linux-mips.org> (raw)
In-Reply-To: <69397FFCADEFD94F8D5A0FC0FDBCBBDEF53B@avtrex-server.hq.avtrex.com>

On Thu, Jan 27, 2005 at 08:54:48PM -0800, David Daney wrote:

> >Why does MIPS/Linux always reserve 32 bytes in the top of each
> >process's kernel stack space.
> 
> Perhaps because the  kernel's ABI requires it?   I beleive that o64 requires stack space for a0 - a3 to be stored there.

Except we don't use o64.

  Ralf

  parent reply	other threads:[~2005-01-29  0:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-28  4:54 Why does MIPS/Linux always reserve 32 bytes in the top of each process's kernel stack space David Daney
2005-01-28  4:54 ` David Daney
2005-01-29  0:02 ` Ralf Baechle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-01-28  2:59 zhan rongkai
2005-01-29  0:03 ` Ralf Baechle

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=20050129000235.GA11602@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=ddaney@avtrex.com \
    --cc=linux-mips@linux-mips.org \
    --cc=zhanrk@gmail.com \
    /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