Messages in this thread | | | Date | Tue, 12 Feb 2002 07:50:48 +1100 | From | Anton Blanchard <> | Subject | Re: thread_info implementation |
| |
> why have thread_info and task_struct to be two different pointers? I'd > prefer two keep one pointer, through everything is accessed, that means > thread_info would be part of task_struct.
Paul and I talked about this and we guessed it is an intel hack so they can use the "mask the stack pointer to get to struct thread_info" trick.
On archs where we use a register to point to current I cant see why we need this thread_info junk. I'd be happy if we could put it all in the task struct for non intel.
Anton - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |