All of lore.kernel.org
 help / color / mirror / Atom feed
From: Igor Russkikh <irusskikh@marvell.com>
To: <netdev@vger.kernel.org>
Cc: "David S . Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	Ariel Elior <aelior@marvell.com>,
	Michal Kalderon <mkalderon@marvell.com>,
	Jesse Brandeburg <jesse.brandeburg@intel.com>,
	"Igor Russkikh" <irusskikh@marvell.com>
Subject: [PATCH v7 net-next 00/10] qed: introduce devlink health support
Date: Sun, 23 Aug 2020 14:19:24 +0300	[thread overview]
Message-ID: <20200823111934.305-1-irusskikh@marvell.com> (raw)

This is a followup implementation after series

https://patchwork.ozlabs.org/project/netdev/cover/20200514095727.1361-1-irusskikh@marvell.com/

This is an implementation of devlink health infrastructure.

With this we are now able to report HW errors to devlink, and it'll take
its own actions depending on user configuration to capture and store the
dump at the bad moment, and to request the driver to recover the device.

So far we do not differentiate global device failures or specific PCI
function failures. This means that some errors specific to one physical
function will affect an entire device. This is not yet fully designed
and verified, will followup in future.

Solution was verified with artificial HW errors generated, existing
tools for dump analysis could be used.

v7: comments from Jesse and Jakub
 - p2: extra edev check
 - p9: removed extra indents
v6: patch 4: changing serial to board.serial and fw to fw.app
v5: improved patch 4 description
v4:
 - commit message and other fixes after Jiri's comments
 - removed one patch (will send to net)
v3: fix uninit var usage in patch 11
v2: fix #include issue from kbuild test robot.

Igor Russkikh (10):
  qed: move out devlink logic into a new file
  qed/qede: make devlink survive recovery
  qed: fix kconfig help entries
  qed: implement devlink info request
  qed: health reporter init deinit seq
  qed: use devlink logic to report errors
  qed*: make use of devlink recovery infrastructure
  qed: implement devlink dump
  qed: align adjacent indent
  qede: make driver reliable on unload after failures

 drivers/net/ethernet/qlogic/Kconfig           |   5 +-
 drivers/net/ethernet/qlogic/qed/Makefile      |   1 +
 drivers/net/ethernet/qlogic/qed/qed.h         |   3 +-
 drivers/net/ethernet/qlogic/qed/qed_dev.c     |   9 +
 drivers/net/ethernet/qlogic/qed/qed_devlink.c | 259 ++++++++++++++++++
 drivers/net/ethernet/qlogic/qed/qed_devlink.h |  20 ++
 drivers/net/ethernet/qlogic/qed/qed_main.c    | 116 +-------
 drivers/net/ethernet/qlogic/qede/qede.h       |   2 +
 drivers/net/ethernet/qlogic/qede/qede_main.c  |  38 ++-
 include/linux/qed/qed_if.h                    |  82 +++---
 10 files changed, 375 insertions(+), 160 deletions(-)
 create mode 100644 drivers/net/ethernet/qlogic/qed/qed_devlink.c
 create mode 100644 drivers/net/ethernet/qlogic/qed/qed_devlink.h

-- 
2.17.1


             reply	other threads:[~2020-08-23 11:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-23 11:19 Igor Russkikh [this message]
2020-08-23 11:19 ` [PATCH v7 net-next 01/10] qed: move out devlink logic into a new file Igor Russkikh
2020-08-23 11:19 ` [PATCH v7 net-next 02/10] qed/qede: make devlink survive recovery Igor Russkikh
2020-08-23 11:19 ` [PATCH v7 net-next 03/10] qed: fix kconfig help entries Igor Russkikh
2020-08-23 11:19 ` [PATCH v7 net-next 04/10] qed: implement devlink info request Igor Russkikh
2020-08-23 11:19 ` [PATCH v7 net-next 05/10] qed: health reporter init deinit seq Igor Russkikh
2020-08-23 11:19 ` [PATCH v7 net-next 06/10] qed: use devlink logic to report errors Igor Russkikh
2020-08-23 11:19 ` [PATCH v7 net-next 07/10] qed*: make use of devlink recovery infrastructure Igor Russkikh
2020-08-23 11:19 ` [PATCH v7 net-next 08/10] qed: implement devlink dump Igor Russkikh
2020-08-23 11:19 ` [PATCH v7 net-next 09/10] qed: align adjacent indent Igor Russkikh
2020-08-23 11:19 ` [PATCH v7 net-next 10/10] qede: make driver reliable on unload after failures Igor Russkikh
2020-08-25  1:01 ` [PATCH v7 net-next 00/10] qed: introduce devlink health support 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=20200823111934.305-1-irusskikh@marvell.com \
    --to=irusskikh@marvell.com \
    --cc=aelior@marvell.com \
    --cc=davem@davemloft.net \
    --cc=jesse.brandeburg@intel.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.