From: randy_dunlap <rdunlap@xenotime.net>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org,
arjanv@infradead.org, guichaz@gmail.com
Subject: Re: [patch] compress the stack layout of do_page_fault(), x86
Date: Sat, 9 Jul 2005 09:44:55 -0700 [thread overview]
Message-ID: <20050709094455.0ef508e3.rdunlap@xenotime.net> (raw)
In-Reply-To: <20050709152924.GA13492@elte.hu>
On Sat, 9 Jul 2005 17:29:24 +0200 Ingo Molnar wrote:
|
| Guillaume noticed a bug in the patch, si_signo should be used instead of
| SIGSEGV. (doh) New patch below.
|
| Ingo
|
| -----
|
| this patch pushes the creation of a rare signal frame (SIGBUS or
| SIGSEGV) into a separate function, thus saving stackspace in the main
| do_page_fault() stackframe. The effect is 132 bytes less of stack used
| by the typical do_page_fault() invocation - resulting in a denser
| cache-layout.
|
| (another minor effect is that in case of kernel crashes that come from a
| pagefault, we add less space to the already existing frame, giving the
| crash functions a slightly higher chance to do their stuff without
| overflowing the stack.)
|
| (the changes also result in slightly cleaner code.)
|
| build and boot tested.
Hi Ingo-
Just to clarify this, "boot tested" does not mean that this
changed code was tested, right?
or do you have a test case that was tested?
Thanks,
---
~Randy
next prev parent reply other threads:[~2005-07-09 16:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-09 14:41 Ingo Molnar
2005-07-09 15:29 ` Ingo Molnar
2005-07-09 16:44 ` randy_dunlap [this message]
2005-07-09 16:46 ` Ingo Molnar
2005-07-10 3:35 ` Chris Wedgwood
[not found] <20050709144116.GA9444@elte.hu.suse.lists.linux.kernel>
[not found] ` <20050709152924.GA13492@elte.hu.suse.lists.linux.kernel>
2005-07-09 17:05 ` Andi Kleen
2005-07-09 17:31 ` Arjan van de Ven
2005-07-09 19:15 ` Andi Kleen
2005-07-09 19:47 ` Arjan van de Ven
2005-07-09 19:42 ` Ingo Molnar
2005-07-10 16:13 ` Andi Kleen
2005-07-11 2:32 ` Ingo Molnar
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=20050709094455.0ef508e3.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@osdl.org \
--cc=arjanv@infradead.org \
--cc=guichaz@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®