Messages in this thread |  | | Date | Wed, 30 Aug 2006 08:03:52 -0400 | | From | Rik van Riel <> | | Subject | Re: Spinlock query |
| |
Rajat Jain wrote: > On 8/30/06, Rik van Riel <riel@surriel.com> wrote: >> Rick Brown wrote: >> > Hi, >> > >> > In my driver (Process context), I have written the following code: >> > >> > -------------------------------------------- >> > spin_lock(lock) >> > ... >> > //Critical section to manipulate driver data >> >> ... interrupt hits here >> interrupt handler tries to grab the spinlock, which is already taken >> *BOOM* >> >> > spin_u lock(lock) >> > --------------------------------------------- >> > > > The interrupt handler TRIES to grab the spinlock, which is already > taken. Why will it "BOOM"? Wouldn't the interrupt handler busy wait, > waiting for the lock? > > Am I missing something here?
Yes, it will busy wait. Forever.
-- What is important? What you want to be true, or what is true? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |