On Sun, 30 Apr 2006 22:33:23 +0800 (CST), Jehnny <[EMAIL PROTECTED]> wrote:
> Why you use the "spin_lock (&ehci->lock)" to > protect the EHCI data structure rather than > spin_lock_irqsave()? If the EHCI interrupt toggle > again when EHCI interrupt handler executing, then the > latter interrupt will busy loop in "spin_lock > (&ehci->lock)" and cause "double-acquire". Is it > correct or I misunderstanding it. Same interrupt handler cannot be entered twice in Linux. How this is done, depends on the platform. If the interrupt controller allows it, the interrupt source is masked. Otherwise, software flags are used. If you detect a situation where an interrupt handler is re-entered, it is a bug in your Linux implementation. Report it to your board vendor. -- Pete ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel