On Mon, Nov 14, 2005 at 09:07:48PM -0500, Lee Revell wrote:
> On Mon, 2005-11-14 at 19:02 -0600, Robert Hancock wrote:
> > 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
>
> Um, but it's really really bad for drivers to do that.
And loading Windows drivers into the kernel isn't ?
I think we're already in no-mans land here.
Remember, we have no clue what those drivers are even doing.
Preemption is the least of its problems.
Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
