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

Robert Hancock
2005-11-15T01:02:54Z

Giridhar Pemmasani wrote:
> Shouldn't I have to prevent scheduler from changing the tasks when executing
> Windows code? Otherwise, kernel gets wrong current thread information,
> which is based on stack pointer. This is the stumbling block for implementing
> private stacks.

As long as preemption is disabled when the driver code is executing I
don't see how this would happen.. I don't know much of how ndiswrapper
does things but if the driver calls back into your code then you'd just
have to change the stack back before doing anything that could schedule.

--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/