From: Dave Hansen <haveblue@us.ibm.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [RFC][PATCH] x86 transition to 4k stacks (0/3)
Date: Mon, 14 Oct 2002 22:59:55 -0700 [thread overview]
Message-ID: <3DABAEDB.9070207@us.ibm.com> (raw)
The kernel currently uses an 8k stack, per task. Here is the
infrastructure needed to allow us to halve that at some point in the
future.
This is a port of work Ben LaHaise did around 2.5.20 time. I split it
up and updated it for the new preempt_count semantics.
I split the original patch up into 3 pieces (apply in this order):
* clean thread info infrastructure (1/3)
- take out all instances of things like (8191&addr) to get
current stack address.
* stack checking (3/3)
- use gcc's profiling features to check for stack overflows upon
entry to functions.
- Warn if the task goes over 4k.
- Panic if the stack gets within 512 bytes of overflowing.
* interrupt stacks (3/3)
- allocate per-cpu interrupt stacks. upon entry to
common_interrupt, switch to the current cpu's stack.
- inherit the interrupted task's preempt count
Any suggestions on how to deal with "gcc -p" and old, buggy versions
of gcc would be appreciated.
--
Dave Hansen
haveblue@us.ibm.com
next reply other threads:[~2002-10-15 5:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 5:59 Dave Hansen [this message]
2002-10-15 15:10 ` [RFC][PATCH] x86 transition to 4k stacks (0/3) Daniel Jacobowitz
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=3DABAEDB.9070207@us.ibm.com \
--to=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.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