[lkml]   [2008]   [Oct]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subjectwhen spin_lock_irq (as opposed to spin_lock_irqsave) is appropriate?
Logically, one piece of kernel code has no way to know whether another
piece of kernel code (or may be hard-/firmware) has disabled some
interrupt line. So it looks like spin_lock_irq should not even exist,
except may be for very specific cases (where we are sure no other piece
of kernel code may run concurrently)?

Sorry for stupid question, I an not actually a HW type of person ...
[unhandled content-type:application/pgp-signature]
 \ /
  Last update: 2008-10-11 17:31    [W:0.051 / U:18.336 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site