From: Matt Mackall <mpm@selenic.com>
To: Pavel Machek <pavel@suse.cz>
Cc: Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org
Subject: [PATCH] x86: trim ACPI sleep stack buffer
Date: Thu, 09 Oct 2008 11:56:21 -0500 [thread overview]
Message-ID: <1223571381.17706.94.camel@calx> (raw)
In-Reply-To: <20081009085649.GC29957@atrey.karlin.mff.cuni.cz>
On Thu, 2008-10-09 at 10:56 +0200, Pavel Machek wrote:
> > We've got:
> >
> > #if defined(CONFIG_SMP) && defined(CONFIG_64BIT)
> > static char temp_stack[10240];
> > #endif
> >
> > and:
> >
> > #ifdef CONFIG_SMP
> > stack_start.sp = temp_stack + 4096;
> > #endif
> >
> > ..which suggests we use at most 4k of the stack?
>
> I guess someone (probably me) was "playing it safe" -- not exactly
> remembering if stack grows down or up. I guess it should be safe to
> change it... will do that.
> Pavel
I've already got a patch, I was just wondering if there was some obscure
architectural reason for it that I wasn't aware of.
x86: trim ACPI sleep stack buffer
x86_64 SMP suspend to RAM uses a 10k temporary stack for saving the
kernel state, but only 4k of it is used. Shrink it to 4k.
Signed-off-by: Matt Mackall <mpm@selenic.com>
diff -r 73d55a1b6c10 arch/x86/kernel/acpi/sleep.c
--- a/arch/x86/kernel/acpi/sleep.c Wed Oct 08 14:48:45 2008 -0500
+++ b/arch/x86/kernel/acpi/sleep.c Thu Oct 09 11:51:54 2008 -0500
@@ -21,7 +21,7 @@
static unsigned long acpi_realmode;
#if defined(CONFIG_SMP) && defined(CONFIG_64BIT)
-static char temp_stack[10240];
+static char temp_stack[4096];
#endif
/**
--
Mathematics is the supreme nostalgia of our time.
next prev parent reply other threads:[~2008-10-09 16:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 0:12 Why is arch/x86/kernel/acpi/sleep.c:temp_stack 10k? Matt Mackall
2008-10-09 8:56 ` Pavel Machek
2008-10-09 16:56 ` Matt Mackall [this message]
2008-10-09 17:19 ` [PATCH] x86: trim ACPI sleep stack buffer Len Brown
2008-10-09 17:23 ` Moore, Robert
2008-10-09 17:41 ` Matt Mackall
2008-10-09 18:07 ` Pavel Machek
2008-10-09 18:35 ` Len Brown
2008-10-09 21:25 ` Rafael J. Wysocki
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=1223571381.17706.94.camel@calx \
--to=mpm@selenic.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pavel@suse.cz \
/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