From: Matt Mackall <mpm@selenic.com>
To: Ingo Molnar <mingo@elte.hu>, Pavel Machek <pavel@suse.cz>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org
Subject: Why is arch/x86/kernel/acpi/sleep.c:temp_stack 10k?
Date: Tue, 30 Sep 2008 19:12:37 -0500 [thread overview]
Message-ID: <1222819957.13453.15.camel@calx> (raw)
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?
--
Mathematics is the supreme nostalgia of our time.
next reply other threads:[~2008-10-01 0:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 0:12 Matt Mackall [this message]
2008-10-09 8:56 ` Why is arch/x86/kernel/acpi/sleep.c:temp_stack 10k? Pavel Machek
2008-10-09 16:56 ` [PATCH] x86: trim ACPI sleep stack buffer Matt Mackall
2008-10-09 17:19 ` 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=1222819957.13453.15.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