> :> *not* preempted except when being interrupted, so there are no > :> 'priorities', per say. Or, rather, the relative priority is strictly > :> that the interrupt takes priority over supervisor code except when > :> disabled by said supervisor code. > : > :But locks with owners wouldn't have to disable interrupts (given that > :we have interrupt threads). What about shared interrupts? You could > :still field and process the interrupt as long as it was for a different > :device. > :Dan Eischen > > The word 'too bad' comes to mind re: shared interrupts. Too bad is not acceptable. If we want to support multi-function PCMCIA/CardBus cards, we *must* do shared interrupts, and multi-function cards are becoming the standard, rather than the exception. Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- Is there spinlocks/semaphores available for drivers? Nikolai Saoukh
- Re: Is there spinlocks/semaphores available for driv... Matthew Dillon
- Re: Is there spinlocks/semaphores available for ... Nikolai Saoukh
- Re: Is there spinlocks/semaphores available ... Matthew Dillon
- Re: Is there spinlocks/semaphores available for driv... Daniel Eischen
- Re: Is there spinlocks/semaphores available for ... Matthew Dillon
- Re: Is there spinlocks/semaphores available ... Matthew Jacob
- Re: Is there spinlocks/semaphores available ... Daniel Eischen
- Re: Is there spinlocks/semaphores availa... Matthew Dillon
- Re: Is there spinlocks/semaphores a... Nate Williams
- Re: Is there spinlocks/semaphor... Matthew Dillon
- Re: Is there spinlocks/sema... Nate Williams
- Re: Is there spinlocks/sema... Mike Smith
- Re: Is there spinlocks/sema... Daniel Eischen
- Re: Is there spinlocks/sema... Matthew Dillon
- Re: Is there spinlocks/sema... Nate Williams
- Re: Is there spinlocks/sema... Daniel Eischen
- Re: Is there spinlocks/sema... Matthew Dillon
- Re: Is there spinlocks/sema... Alfred Perlstein
- Re: Is there spinlocks/sema... Matthew Dillon