correct locking primitive?

Nicholas Murphy halcyonic at gmail.com
Tue Aug 11 22:01:30 EDT 2015


So reading this:

https://www.kernel.org/pub/linux/kernel/people/rusty/kernel-locking/x137.html

…led me to believe that spin_lock_bh() was the correct primitive to use within a callback from a high resolution timer, but that didn’t work.  Instead using spin_lock_irqsave() did work, however.  Can someone explain why?

Thanks,
Nick


More information about the Kernelnewbies mailing list