correct locking primitive?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies




[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux