Parity errors might happen in the device's memories due to momentary bit
flips which are caused by radiation.
Errors that are not correctable initiate a process kill event, which blocks
the device access towards the host and the network, and a recovery process
is started in the management FW and in the driver.

This series adds the support of this process in the qed core module and in
the qede driver (patches 2 & 3).
Patch 1 in the series revises the load sequence, to avoid PCI errors that
might be observed during a recovery process.

Changes in v2:
        - Addressed issue found in https://patchwork.ozlabs.org/patch/1030545/
          The change was done be removing the enum and passing a boolean to
          the related functions.

Tomer Tayar (3):
  qed: Revise load sequence to avoid PCI errors
  qed: Add infrastructure for error detection and recovery
  qede: Error recovery process

 drivers/net/ethernet/qlogic/qed/qed.h          |   5 +-
 drivers/net/ethernet/qlogic/qed/qed_dev.c      | 158 +++++++------
 drivers/net/ethernet/qlogic/qed/qed_dev_api.h  |  12 +
 drivers/net/ethernet/qlogic/qed/qed_hsi.h      |   2 +-
 drivers/net/ethernet/qlogic/qed/qed_hw.c       |  11 +
 drivers/net/ethernet/qlogic/qed/qed_int.c      | 126 +++++------
 drivers/net/ethernet/qlogic/qed/qed_int.h      |   3 +
 drivers/net/ethernet/qlogic/qed/qed_main.c     |  30 +++
 drivers/net/ethernet/qlogic/qed/qed_mcp.c      | 115 ++++++++++
 drivers/net/ethernet/qlogic/qed/qed_mcp.h      |  42 ++++
 drivers/net/ethernet/qlogic/qed/qed_reg_addr.h |   2 +
 drivers/net/ethernet/qlogic/qed/qed_spq.c      |  22 ++
 drivers/net/ethernet/qlogic/qed/qed_sriov.c    |   9 +-
 drivers/net/ethernet/qlogic/qede/qede.h        |   3 +
 drivers/net/ethernet/qlogic/qede/qede_main.c   | 292 ++++++++++++++++++++-----
 drivers/net/ethernet/qlogic/qede/qede_rdma.c   |  63 ++++--
 include/linux/qed/qed_if.h                     |  20 ++
 include/linux/qed/qede_rdma.h                  |  10 +-
 18 files changed, 723 insertions(+), 202 deletions(-)

-- 
1.8.3.1

Reply via email to