Lee Revell wrote:
As long as preemption is disabled when the driver code is executing
Um, but it's really really bad for drivers to do that.
Normally yes.. but that may be a sacrifice that may have to be made
considering what ndiswrapper is doing - inserting blobs of code into the
kernel that were never designed to run there. I would think that would
be something you would want to do with such a driver regardless of stack
switching - do we have any way of knowing whether the Windows driver is
doing some timing-dependent thing that will cause bad things to happen
if we take away the CPU from it in the middle?
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [email protected]
Home Page: http://www.roberthancock.com/
-
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]
