Re: PANIC: blockable slep lock (sx) msi _at_ ....msi.c:374

From: Scott Long <scottl_at_samsco.org>
Date: Fri, 04 May 2007 15:57:26 -0600
Julian Elischer wrote:
> John Baldwin wrote:
> 
>>
>> This is wrong because once you do critical_enter(), you are free to 
>> assume that you won't do a context switch until you critical_exit(), 
>> and sx_xlock() would violate that if it blocked on the lock.
> 
> wellllll critical enter doesn't block interupts so it's true if you 
> don't call
> an interrupt as a context switch.
> (it doesn't SWITCH contexts but it does step into a different context.)
> 

Yes, interrupts are serviced when a critical section is entered, but 
ithreads are not run on the same CPU until the critical section is 
exited.  This has been debated quite a bit over the last few years, but
I it's a good compromise.  This implications just don't seem to be 
documented well, especially for those who need a protected, 
uninterruptable context for doing time-critical operations.

Scott
Received on Fri May 04 2007 - 19:57:34 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:09 UTC