From: Jun Sun <jsun@mvista.com>
To: Vivien Chappelier <vivienc@nerim.net>
Cc: Ralf Baechle <ralf@oss.sgi.com>,
linux-mips@linux-mips.org, jsun@mvista.com
Subject: Re: [PATCH 2.5] r4k_switch task_struct/thread_info fixes
Date: Fri, 7 Feb 2003 10:40:20 -0800 [thread overview]
Message-ID: <20030207104020.K13258@mvista.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0302071019550.1913-100000@melkor>; from vivienc@nerim.net on Fri, Feb 07, 2003 at 10:29:16AM +0100
On Fri, Feb 07, 2003 at 10:29:16AM +0100, Vivien Chappelier wrote:
> On Thu, 6 Feb 2003, Jun Sun wrote:
>
> > Actually the following hunks are not right. ST_OFF
> > should be applied against the task_struct, which is a0,
> > not thread_info (t3).
>
> In 2.4 yes, not in 2.5.
>
You are right. I got misled. I thought task struct has 2 page
size and thread_info is allocated from slab. It should be reverse.
> include/linux/sched.h:469
> > union thread_union {
> > struct thread_info thread_info;
> > unsigned long stack[INIT_THREAD_SIZE/sizeof(long)];
> > };
>
> That means the top of the stack is actually at (task->thread_info +
> KERNEL_STACK_SIZE) in 2.5. See for example arch/mips64/kernel/ptrace.c:107
>
> > Also see my next email before you rush into trying :-)
>
> Ok, I'll look at it later.
>
It turns I made a rather stupid comment there as well. See it there. :-)
Jun
prev parent reply other threads:[~2003-02-07 18:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-03 22:21 [PATCH 2.5] r4k_switch task_struct/thread_info fixes Vivien Chappelier
2003-02-04 12:54 ` Ralf Baechle
2003-02-07 0:36 ` Jun Sun
2003-02-07 9:29 ` Vivien Chappelier
2003-02-07 18:40 ` Jun Sun [this message]
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=20030207104020.K13258@mvista.com \
--to=jsun@mvista.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@oss.sgi.com \
--cc=vivienc@nerim.net \
/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.