Re: [2.6 patch] i386: always use 4k stacks

From: Benjamin LaHaise
Date: Mon Nov 14 2005 - 14:21:00 EST


On Mon, Nov 14, 2005 at 08:00:07PM +0100, Olivier Galibert wrote:
> Couldn't ndiswrapper have its own private stack to switch to when
> calling the windows driver, or are there still things hanging off the
> end of the stack area?

It's possible, but would need a change to how the kernel finds the thread
local data (which is currently done by masking off the stack pointer).
There are certainly a few ways of doing this, like using tr to find out
which cpu we're on and then indexing into the thread info state.

-ben
--
"Time is what keeps everything from happening all at once." -- John Wheeler
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/