From: Igor Russkikh <irusskikh@marvell.com>
To: <netdev@vger.kernel.org>
Cc: "David S . Miller" <davem@davemloft.net>,
Ariel Elior <aelior@marvell.com>,
Michal Kalderon <mkalderon@marvell.com>,
Denis Bolotin <dbolotin@marvell.com>,
Jakub Kicinski <kuba@kernel.org>,
Igor Russkikh <irusskikh@marvell.com>
Subject: [PATCH v2 net-next 00/11] net: qed/qede: critical hw error handling
Date: Thu, 14 May 2020 12:57:16 +0300 [thread overview]
Message-ID: <20200514095727.1361-1-irusskikh@marvell.com> (raw)
FastLinQ devices as a complex systems may observe various hardware
level error conditions, both severe and recoverable.
Driver is able to detect and report this, but so far it only did
trace/dmesg based reporting.
Here we implement an extended hw error detection, service task
handler captures a dump for the later analysis.
I also resubmit a patch from Denis Bolotin on tx timeout handler,
addressing David's comment regarding recovery procedure as an extra
reaction on this event.
v2:
Removing the patch with ethtool dump and udev magic. Its quite isolated,
I'm working on devlink based logic for this separately.
v1:
https://patchwork.ozlabs.org/project/netdev/cover/cover.1588758463.git.irusskikh@marvell.com/
Denis Bolotin (1):
net: qede: Implement ndo_tx_timeout
Igor Russkikh (10):
net: qed: adding hw_err states and handling
net: qede: add hw err scheduled handler
net: qed: invoke err notify on critical areas
net: qed: critical err reporting to management firmware
net: qed: cleanup debug related declarations
net: qed: attention clearing properties
net: qede: optional hw recovery procedure
net: qed: introduce critical fan failure handler
net: qed: introduce critical hardware error handler
net: qed: fix bad formatting
drivers/net/ethernet/qlogic/qed/qed.h | 16 +-
drivers/net/ethernet/qlogic/qed/qed_debug.c | 26 +-
drivers/net/ethernet/qlogic/qed/qed_dev.c | 4 +-
drivers/net/ethernet/qlogic/qed/qed_hsi.h | 49 +++-
drivers/net/ethernet/qlogic/qed/qed_hw.c | 42 ++-
drivers/net/ethernet/qlogic/qed/qed_hw.h | 15 ++
drivers/net/ethernet/qlogic/qed/qed_int.c | 40 ++-
drivers/net/ethernet/qlogic/qed/qed_int.h | 11 +
drivers/net/ethernet/qlogic/qed/qed_main.c | 34 +++
drivers/net/ethernet/qlogic/qed/qed_mcp.c | 254 ++++++++++++++++++
drivers/net/ethernet/qlogic/qed/qed_mcp.h | 28 ++
drivers/net/ethernet/qlogic/qed/qed_spq.c | 16 +-
drivers/net/ethernet/qlogic/qede/qede.h | 14 +-
.../net/ethernet/qlogic/qede/qede_ethtool.c | 24 ++
drivers/net/ethernet/qlogic/qede/qede_main.c | 147 +++++++++-
include/linux/qed/qed_if.h | 26 +-
16 files changed, 700 insertions(+), 46 deletions(-)
--
2.17.1
next reply other threads:[~2020-05-14 9:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 9:57 Igor Russkikh [this message]
2020-05-14 9:57 ` [PATCH v2 net-next 01/11] net: qed: adding hw_err states and handling Igor Russkikh
2020-05-14 9:57 ` [PATCH v2 net-next 02/11] net: qede: add hw err scheduled handler Igor Russkikh
2020-05-14 9:57 ` [PATCH v2 net-next 03/11] net: qed: invoke err notify on critical areas Igor Russkikh
2020-05-14 9:57 ` [PATCH v2 net-next 04/11] net: qed: critical err reporting to management firmware Igor Russkikh
2020-05-14 9:57 ` [PATCH v2 net-next 05/11] net: qed: cleanup debug related declarations Igor Russkikh
2020-05-14 9:57 ` [PATCH v2 net-next 06/11] net: qed: attention clearing properties Igor Russkikh
2020-05-14 9:57 ` [PATCH v2 net-next 07/11] net: qede: optional hw recovery procedure Igor Russkikh
2020-05-14 9:57 ` [PATCH v2 net-next 08/11] net: qede: Implement ndo_tx_timeout Igor Russkikh
2020-05-14 9:57 ` [PATCH v2 net-next 09/11] net: qed: introduce critical fan failure handler Igor Russkikh
2020-05-14 9:57 ` [PATCH v2 net-next 10/11] net: qed: introduce critical hardware error handler Igor Russkikh
2020-05-14 9:57 ` [PATCH v2 net-next 11/11] net: qed: fix bad formatting Igor Russkikh
2020-05-14 19:06 ` [PATCH v2 net-next 00/11] net: qed/qede: critical hw error handling Jakub Kicinski
2020-05-14 19:40 ` [EXT] " Igor Russkikh
2020-05-14 20:02 ` Jakub Kicinski
2020-05-14 20:09 ` Igor Russkikh
2020-05-14 20:01 ` David Miller
2020-05-14 20:09 ` David Miller
2020-05-14 20:22 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200514095727.1361-1-irusskikh@marvell.com \
--to=irusskikh@marvell.com \
--cc=aelior@marvell.com \
--cc=davem@davemloft.net \
--cc=dbolotin@marvell.com \
--cc=kuba@kernel.org \
--cc=mkalderon@marvell.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.