aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/net/ethernet/sfc/mcdi.c
diff options
context:
space:
mode:
authorBen Hutchings <bhutchings@solarflare.com>2012-01-05 20:14:10 +0000
committerBen Hutchings <bhutchings@solarflare.com>2012-01-27 00:10:52 +0000
commit1646a6f352a6f70fcca828589ed04797aa09d494 (patch)
tree7f39f32e75140e831c26dd57caa7c28515252053 /drivers/net/ethernet/sfc/mcdi.c
parentPartly revert "sfc: Handle serious errors in exactly one interrupt handler" (diff)
downloadlinux-dev-1646a6f352a6f70fcca828589ed04797aa09d494.tar.xz
linux-dev-1646a6f352a6f70fcca828589ed04797aa09d494.zip
sfc: Clean up test interrupt handling
Interrupts are normally generated by the event queues, moderated by timers. However, they may also be triggered by detection of a 'fatal' error condition (e.g. memory parity error) or by the host writing to certain CSR fields as part of a self-test. The IRQ level/index used for these on Falcon rev B0 and Siena is set by the KER_INT_LEVE_SEL field and cached by the driver in efx_nic::fatal_irq_level. Since this value is also relevant to self-tests rename the field to just 'irq_level'. Avoid unnecessary cache traffic by using a per-channel 'last_irq_cpu' field and only writing to the per-controller field when the interrupt matches efx_nic::irq_level. Remove the volatile qualifier and use ACCESS_ONCE in the places we read these fields. Signed-off-by: Ben Hutchings <bhutchings@solarflare.com>
Diffstat (limited to 'drivers/net/ethernet/sfc/mcdi.c')
0 files changed, 0 insertions, 0 deletions