On Wed, Jun 17, 2015 at 05:18:27PM +0530, Vineet Gupta wrote: > Turns out that it is possible to implement NMI on ARCv2 in a pretty > straightforward way. > > Our RTOS Guru, Chuck, told me off list, that instead of using CLRI / SETI, we can > use SETI with different args which would keep the stat32.IE enabled all the times, > but wiggle the stat32.E[ ] to change the intr prio level, effectively locking out > only lower prio interrupts in any local_irq_save() / restore() region. Nice. > But isn't this defying the irq disable/enable semantics and could lead to > potential breach of *some* critical section. Well only if you then hand out interrupts for that priority level without treating them as NMIs. Note that NMIs do not nest, so if your hardware can raise multiple interrupts for any one level it needs to mask the level in your handler's entry code. > Neverthless, doing this requires some more changes in ARCv2 support code - so for > now we will go with the normal interrupts and later bolt on the NMI emulation. Sure, smalls steps etc.. :-) -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
