when spin_lock_irq (as opposed to spin_lock_irqsave) is appropriate?

Andrey Borzenkov
2008-10-11T15:29:18Z

[-- Attachment #1: Type: text/plain, Size: 387 bytes --]

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 ...

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]