Messages in this thread | | | Date | Mon, 14 Nov 2005 19:02:46 -0600 | From | Robert Hancock <> | Subject | Re: [2.6 patch] i386: always use 4k stacks |
| |
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/
- 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/
| |