From: Jakub Kicinski <kuba@kernel.org>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
andrew+netdev@lunn.ch, horms@kernel.org, alexanderduyck@fb.com,
jacob.e.keller@intel.com, Jakub Kicinski <kuba@kernel.org>
Subject: [PATCH net-next 0/9] eth: fbnic: add devlink health support for FW crashes and OTP mem corruptions
Date: Fri, 12 Sep 2025 13:14:19 -0700 [thread overview]
Message-ID: <20250912201428.566190-1-kuba@kernel.org> (raw)
Add support for FW crash detection and a corresponding delink health
reporter. Add a reporter for checking OTP memory health.
The output is not particularly exciting:
# devlink health show
pci/0000:01:00.0:
reporter fw
state healthy error 0 recover 0 auto_dump true
reporter otp
state healthy error 0 recover 0 auto_dump true
# devlink health diagnose pci/0000:01:00.0 reporter fw
FW uptime: 0
# devlink health dump show pci/0000:01:00.0 reporter fw
FW coredump:
5a 45 01 00 04 00 06 00 00 00 00 00 4d 01 00 d0
.. lots of hex follows ..
# devlink health dump show pci/0000:01:00.0 reporter otp
OTP:
Status: 0 Data: 0 ECC: 0
Jakub Kicinski (9):
eth: fbnic: make fbnic_fw_log_write() parameter const
eth: fbnic: use fw uptime to detect fw crashes
eth: fbnic: factor out clearing the action TCAM
eth: fbnic: reprogram TCAMs after FW crash
eth: fbnic: support allocating FW completions with extra space
eth: fbnic: support FW communication for core dump
eth: fbnic: add FW health reporter
eth: fbnic: report FW uptime in health diagnose
eth: fbnic: add OTP health reporter
.../device_drivers/ethernet/meta/fbnic.rst | 19 ++
drivers/net/ethernet/meta/fbnic/fbnic.h | 13 +
drivers/net/ethernet/meta/fbnic/fbnic_csr.h | 18 ++
drivers/net/ethernet/meta/fbnic/fbnic_fw.h | 46 ++++
.../net/ethernet/meta/fbnic/fbnic_fw_log.h | 2 +-
.../net/ethernet/meta/fbnic/fbnic_devlink.c | 235 +++++++++++++++++
drivers/net/ethernet/meta/fbnic/fbnic_fw.c | 239 +++++++++++++++++-
.../net/ethernet/meta/fbnic/fbnic_fw_log.c | 2 +-
drivers/net/ethernet/meta/fbnic/fbnic_pci.c | 39 ++-
drivers/net/ethernet/meta/fbnic/fbnic_rpc.c | 57 +++--
10 files changed, 642 insertions(+), 28 deletions(-)
--
2.51.0
next reply other threads:[~2025-09-12 20:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-12 20:14 Jakub Kicinski [this message]
2025-09-12 20:14 ` [PATCH net-next 1/9] eth: fbnic: make fbnic_fw_log_write() parameter const Jakub Kicinski
2025-09-12 20:14 ` [PATCH net-next 2/9] eth: fbnic: use fw uptime to detect fw crashes Jakub Kicinski
2025-09-15 9:58 ` Simon Horman
2025-09-15 15:16 ` Jakub Kicinski
2025-09-15 17:48 ` Simon Horman
2025-09-12 20:14 ` [PATCH net-next 3/9] eth: fbnic: factor out clearing the action TCAM Jakub Kicinski
2025-09-12 20:14 ` [PATCH net-next 4/9] eth: fbnic: reprogram TCAMs after FW crash Jakub Kicinski
2025-09-12 20:14 ` [PATCH net-next 5/9] eth: fbnic: support allocating FW completions with extra space Jakub Kicinski
2025-09-12 20:14 ` [PATCH net-next 6/9] eth: fbnic: support FW communication for core dump Jakub Kicinski
2025-09-12 20:14 ` [PATCH net-next 7/9] eth: fbnic: add FW health reporter Jakub Kicinski
2025-09-12 20:14 ` [PATCH net-next 8/9] eth: fbnic: report FW uptime in health diagnose Jakub Kicinski
2025-09-12 20:14 ` [PATCH net-next 9/9] eth: fbnic: add OTP health reporter Jakub Kicinski
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=20250912201428.566190-1-kuba@kernel.org \
--to=kuba@kernel.org \
--cc=alexanderduyck@fb.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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.