Re: Quick aic7xxx bug hunt...

["Justin T. Gibbs" <gibbs@scsiguy.com>]

>> For all of these delays, I'd be more than happy to make them all into
>> sleeps if I can tell, from inside ahc_delay() if I'm in a context where
>> it is safe to sleep.  On the other platforms that this core code runs on
>> I'm usually not in a context where it is safe to sleep, so I don't want
>> to switch to using a different driver primitive.
> 
> For Linux it's unconditionally safe, and other platforms is sounds like
> it's unconditionally not.  So, s/ahc_delay/ahc_sleep/ for the places I
> pointed out, and just make ahc_delay==ahc_sleep on non-Linux platforms
> (or any similarly-functioning solution)

So you can sleep while in an interrupt context?  I didn't know that
2.5 had switched to using interrupt threads or some similar construct.

> It's pretty much impossible to detect if you are inside certain
> spinlocks, in a generic fashion.

In 2.5, I should only need to release my own host lock assuming it is
held.

--
Justin