Kernel code heavily uses the spinlock primitives
spin_lock_irqsave/restore plus local interrupt disabling/ enabling, all across the code.
Is there a possibility that the interrupts might get
missed in this small window
disable interrupts
.............
............. <<<<<<<<<<<---------------------- interrupts is trigerred here
enable interrupts
specially when the irq
affinity has been set to the same core on which the
above mentioned code (disabling / enabling the irq's)
runs?
How the linux deals with this kind of scenario?
spin_lock_irqsave/restore plus local interrupt disabling/ enabling, all across the code.
Is there a possibility that the interrupts might get
missed in this small window
disable interrupts
.............
............. <<<<<<<<<<<---------------------- interrupts is trigerred here
enable interrupts
specially when the irq
affinity has been set to the same core on which the
above mentioned code (disabling / enabling the irq's)
runs?
How the linux deals with this kind of scenario?
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies