diff options
author | Vineet Gupta <vgupta@synopsys.com> | 2014-11-15 14:30:08 +0300 |
---|---|---|
committer | Vineet Gupta <vgupta@synopsys.com> | 2015-06-22 11:36:55 +0300 |
commit | 4de0e52867d831057676340271d21cfb920eac1c (patch) | |
tree | 2107aea2b3856bcf4156d4128243d9b2d08d2e81 /net/rxrpc/ar-recvmsg.c | |
parent | 0d7b8855a05c099a5c65a8d49a1e604198021f56 (diff) | |
download | linux-4de0e52867d831057676340271d21cfb920eac1c.tar.xz |
ARCv2: STAR 9000814690: Really Re-enable interrupts to avoid deadlocks
The issue was, on HS when interrupt is taken, IRQ_ACT is set and that is
NOT cleared unless we do RTIE (or manually clear it). Linux interrupt
handling has top and bottom halves. Latter lead to softirqs (which can
reschedule) AND expect interrupts to be REALLY re-enabled which was NOT
happening for us since we only SETI, dont clear IRQ_ACT
So we can have a state when both cores have taken interrupt (IRQ_ACT set),
get rescheduled, both send IPI and wait in CSD lock which will never be
cleared as cores can't take the pending IPI IRQ due to existing IRQ_ACT
set.
So local_irq_enable() now drops the IRQ_ACT.act bit to re-enable IRQs.
Signed-off-by: Vineet Gupta <vgupta@synopsys.com>
Diffstat (limited to 'net/rxrpc/ar-recvmsg.c')
0 files changed, 0 insertions, 0 deletions