Messages in this thread | | | From | Andrey Borzenkov <> | Subject | when spin_lock_irq (as opposed to spin_lock_irqsave) is appropriate? | Date | Sat, 11 Oct 2008 19:29:01 +0400 |
| |
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] | |