summaryrefslogtreecommitdiffstats
path: root/net/socket.c
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2008-04-26 02:19:18 -0700
committerDavid S. Miller <davem@davemloft.net>2008-04-26 21:41:15 -0700
commit227c3311786dbe64cb221e63d53817f98240e587 (patch)
treed2dbe622686da55cc2e1b44d65b595f293838fa7 /net/socket.c
parentc3bf9bc243092c53946fd6d8ebd6dc2f4e572d48 (diff)
downloadop-kernel-dev-227c3311786dbe64cb221e63d53817f98240e587.zip
op-kernel-dev-227c3311786dbe64cb221e63d53817f98240e587.tar.gz
sparc64: Fix wedged irq regression.
Kernel bugzilla 10273 As reported by Jos van der Ende, ever since commit 5a606b72a4309a656cd1a19ad137dc5557c4b8ea ("[SPARC64]: Do not ACK an INO if it is disabled or inprogress.") sun4u interrupts can get stuck. What this changset did was add the following conditional to the various IRQ chip ->enable() handlers on sparc64: if (unlikely(desc->status & (IRQ_DISABLED|IRQ_INPROGRESS))) return; which is correct, however it means that special care is needed in the ->enable() method. Specifically we must put the interrupt into IDLE state during an enable, or else it might never be sent out again. Setting the INO interrupt state to IDLE resets the state machine, the interrupt input to the INO is retested by the hardware, and if an interrupt is being signalled by the device, the INO moves back into TRANSMIT state, and an interrupt vector is sent to the cpu. The two sun4v IRQ chip handlers were already doing this properly, only sun4u got it wrong. Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/socket.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud