On some architectures, spin_lock_irqsave() re-enables interrupts when
spinning while waiting for the lock to become available. The list
of archs includes i386, powerpc and ia64. Others leave interrupts
disabled while spinning (x86_64, arm, alpha). They just define
__raw_spin_lock_flags to be the same as __raw_spin_lock. (And
because predication is so efficient, ia64 does the opposite:
it uses __raw_spin_lock_flags for everything -- a neat trick.)
Shouldn't there be a standard way of doing this? Is there any practical
difference in behavior?
--
Chuck
"Penguins don't come from next door, they come from the Antarctic!"
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
