RE: 53c400 driver

From: Dunlap, Randy (randy.dunlap@intel.com)
Date: Tue Nov 21 2000 - 18:51:47 EST


JE's UHCI driver (drivers/usb/uhci.[hc]) uses
nested_lock() and nested_unlock() for this.
Maybe it could help.

~Randy
_______________________________________________
|randy.dunlap_at_intel.com 503-677-5408|
|NOTE: Any views presented here are mine alone|
|& may not represent the views of my employer.|
-----------------------------------------------

> -----Original Message-----
> From: Alan Cox [mailto:alan@lxorguk.ukuu.org.uk]
> Sent: Tuesday, November 21, 2000 3:48 PM
> To: maillist@chello.nl
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: 53c400 driver
>
>
> > 53c400a non-PNP still lock this system hard. It starts
> barking about a
> > busy SCSI bus, and then I can fsck again.
> >
> > To Alan : How hard is it to get thing beast (53c400 and
> family) to be SMP
> > safe ?? Or is it better to start over again ?
>
> The problem is that the code takes spinlocks recursively. The original
> code (see 2.0's 5380 generic C code) uses cli/sti. It was converted to
> use spin_lock() but not allowing for the recursive locking
> cases. I tried
> to untangle the code paths but they are so ugly and some of
> the code is
> sufficiently messy and unmaintained (for about 6 years) that I gave up
> trying to decode it.
>
> Alan
>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/
>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Thu Nov 23 2000 - 21:00:22 EST