From: Dave Hansen <haveblue@us.ibm.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: William Lee Irwin III <wli@holomorphy.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
lse-tech <lse-tech@lists.sourceforge.net>
Subject: Re: 2.5.69-mjb1
Date: Mon, 12 May 2003 08:05:15 -0700 [thread overview]
Message-ID: <3EBFB82B.8040509@us.ibm.com> (raw)
In-Reply-To: 21850000.1052743254@[10.10.2.4]
Martin J. Bligh wrote:
> --On Monday, May 12, 2003 06:29:39 -0700 William Lee Irwin III <wli@holomorphy.com> wrote:
>
>
>>On Sat, May 10, 2003 at 08:44:09PM -0700, Martin J. Bligh wrote:
>>
>>>thread_info_cleanup (4K stacks pt 1) Dave Hansen / Ben LaHaise
>>> Prep work to reduce kernel stacks to 4K
>>>interrupt_stacks (4K stacks pt 2) Dave Hansen / Ben LaHaise
>>> Create a per-cpu interrupt stack.
>>>stack_usage_check (4K stacks pt 3) Dave Hansen / Ben LaHaise
>>> Check for kernel stack overflows.
>>>4k_stack (4K stacks pt 4) Dave Hansen
>>> Config option to reduce kernel stacks to 4K
>>
>>
>>diff -urpN linux-2.5.69/include/asm-i386/processor.h kstk-2.5.69-1/include/asm-i386/processor.h
>>--- linux-2.5.69/include/asm-i386/processor.h 2003-05-04 16:53:00.000000000 -0700
>>+++ kstk-2.5.69-1/include/asm-i386/processor.h 2003-05-12 06:05:39.000000000 -0700
>>@@ -470,8 +470,8 @@ extern int kernel_thread(int (*fn)(void
>> extern unsigned long thread_saved_pc(struct task_struct *tsk);
>>
>> unsigned long get_wchan(struct task_struct *p);
>>-#define KSTK_EIP(tsk) (((unsigned long *)(4096+(unsigned long)(tsk)->thread_info))[1019])
>>-#define KSTK_ESP(tsk) (((unsigned long *)(4096+(unsigned long)(tsk)->thread_info))[1022])
>>+#define KSTK_EIP(task) (((unsigned long *)(task)->thread_info)[THREAD_SIZE/sizeof(unsigned long) - 5])
>>+#define KSTK_ESP(task) (((unsigned long *)(task)->thread_info)[THREAD_SIZE/sizeof(unsigned long) - 2])
>>
>> struct microcode {
>> unsigned int hdrver;
>
> Can I get some sort of vague explanation please? ;-)
Wow, that's intuitive :)
They're trying to access the variables that have been pushed onto the
top of the stack. The thread_info field points to the bottom of the
kernel's stack (no matter how big it is). I don't know where the -5 and
-2 come from. It needs a big, fat stinking comment.
--
Dave Hansen
haveblue@us.ibm.com
next prev parent reply other threads:[~2003-05-12 14:54 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-11 3:44 2.5.69-mjb1 Martin J. Bligh
2003-05-11 13:33 ` 2.5.69-mjb1 Zwane Mwaikambo
2003-05-11 13:12 ` 2.5.69-mjb1 Martin J. Bligh
2003-05-12 13:29 ` 2.5.69-mjb1 William Lee Irwin III
2003-05-12 12:40 ` 2.5.69-mjb1 Martin J. Bligh
2003-05-12 15:03 ` 2.5.69-mjb1 William Lee Irwin III
2003-05-12 13:07 ` 2.5.69-mjb1 Martin J. Bligh
2003-05-12 15:34 ` 2.5.69-mjb1 Dave Hansen
2003-05-12 13:43 ` 2.5.69-mjb1 Martin J. Bligh
2003-05-12 15:11 ` 2.5.69-mjb1 Dave Hansen
2003-05-12 15:05 ` Dave Hansen [this message]
2003-05-13 1:23 ` [Lse-tech] 2.5.69-mjb1 William Lee Irwin III
2003-05-13 3:41 ` Martin J. Bligh
2003-05-13 6:27 ` William Lee Irwin III
2003-05-13 6:42 ` Andi Kleen
2003-05-12 20:51 ` 2.5.69-mjb1: undefined reference to `blk_queue_empty' Adrian Bunk
2003-05-13 3:51 ` Martin J. Bligh
2003-05-13 7:18 ` Bharata B Rao
2003-05-13 13:58 ` Martin J. Bligh
2003-05-13 18:11 ` Jens Axboe
2003-05-14 8:08 ` Bharata B Rao
2003-05-14 8:32 ` Jens Axboe
2003-05-15 4:07 ` Bharata B Rao
2003-05-15 7:29 ` Jens Axboe
2003-05-15 9:16 ` Bharata B Rao
2003-05-15 12:52 ` Martin J. Bligh
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=3EBFB82B.8040509@us.ibm.com \
--to=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=mbligh@aracnet.com \
--cc=wli@holomorphy.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.