Date: Mon, 14 Nov 2005 20:22:30 -0600
From: Robert Hancock <hancockr@shaw.ca>
Subject: Re: [2.6 patch] i386: always use 4k stacks
In-reply-to: <1132020468.27215.25.camel@mindpipe>
To: Lee Revell <rlrevell@joe-job.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Message-id: <43794666.7020600@shaw.ca>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7bit
References: <58MJb-2Sn-37@gated-at.bofh.it> <58NvO-46M-23@gated-at.bofh.it>
 <58Rpx-1m6-11@gated-at.bofh.it> <58UGF-6qR-27@gated-at.bofh.it>
 <58UQf-6Da-3@gated-at.bofh.it> <437933B6.1000503@shaw.ca>
 <1132020468.27215.25.camel@mindpipe>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1017
Lines: 23

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 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/