From: Ralf Baechle <ralf@linux-mips.org>
To: zhan rongkai <zhanrk@gmail.com>
Cc: 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:03:08 +0100 [thread overview]
Message-ID: <20050129000308.GB11602@linux-mips.org> (raw)
In-Reply-To: <73e62045050127185929c3bdf7@mail.gmail.com>
On Fri, Jan 28, 2005 at 10:59:26AM +0800, zhan rongkai wrote:
> Why does MIPS/Linux always reserve 32 bytes in the top of each
> process's kernel stack space.
Paranoia.
Ralf
next prev 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 2:59 Why does MIPS/Linux always reserve 32 bytes in the top of each process's kernel stack space zhan rongkai
2005-01-29 0:03 ` Ralf Baechle [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-28 4:54 David Daney
2005-01-28 4:54 ` David Daney
2005-01-29 0:02 ` 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=20050129000308.GB11602@linux-mips.org \
--to=ralf@linux-mips.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.