From: Mateusz Polchlopek <mateusz.polchlopek@intel.com>
To: intel-wired-lan@lists.osuosl.org
Cc: apw@canonical.com, joe@perches.com, dwaipayanray1@gmail.com,
lukas.bulwahn@gmail.com, akpm@linux-foundation.org,
willemb@google.com, edumazet@google.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Mateusz Polchlopek <mateusz.polchlopek@intel.com>
Subject: [Intel-wired-lan] [PATCH iwl-next v1 0/6] Add support for devlink health events
Date: Wed, 3 Jul 2024 08:59:16 -0400 [thread overview]
Message-ID: <20240703125922.5625-1-mateusz.polchlopek@intel.com> (raw)
Reports for two kinds of events are implemented, Malicious Driver
Detection (MDD) and Tx hang.
Patches 1, 2: minor core improvements (checkpatch.pl and devlink extension)
Patches 3, 4, 5: ice devlink health infra + straightforward status reports
Patch 6: extension to dump also skb on Tx hang, this patch have much of
copy-paste from:
- net/core/skbuff.c (function skb_dump() - modified to dump into buffer)
- lib/hexdump.c (function print_hex_dump() - adjusted)
Ben Shelton (1):
ice: Add MDD logging via devlink health
Przemek Kitszel (5):
checkpatch: don't complain on _Generic() use
devlink: add devlink_fmsg_put() macro
ice: add Tx hang devlink health reporter
ice: print ethtool stats as part of Tx hang devlink health reporter
ice: devlink health: dump also skb on Tx hang
drivers/net/ethernet/intel/ice/Makefile | 1 +
.../intel/ice/devlink/devlink_health.c | 485 ++++++++++++++++++
.../intel/ice/devlink/devlink_health.h | 45 ++
drivers/net/ethernet/intel/ice/ice.h | 2 +
drivers/net/ethernet/intel/ice/ice_ethtool.c | 10 +-
drivers/net/ethernet/intel/ice/ice_ethtool.h | 2 +
.../ethernet/intel/ice/ice_ethtool_common.h | 19 +
drivers/net/ethernet/intel/ice/ice_main.c | 17 +-
include/net/devlink.h | 11 +
scripts/checkpatch.pl | 2 +
10 files changed, 586 insertions(+), 8 deletions(-)
create mode 100644 drivers/net/ethernet/intel/ice/devlink/devlink_health.c
create mode 100644 drivers/net/ethernet/intel/ice/devlink/devlink_health.h
create mode 100644 drivers/net/ethernet/intel/ice/ice_ethtool_common.h
--
2.38.1
next reply other threads:[~2024-07-03 13:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 12:59 Mateusz Polchlopek [this message]
2024-07-03 12:59 ` [Intel-wired-lan] [PATCH iwl-next v1 1/6] checkpatch: don't complain on _Generic() use Mateusz Polchlopek
2024-07-08 12:41 ` Simon Horman
2024-07-03 12:59 ` [Intel-wired-lan] [PATCH iwl-next v1 2/6] devlink: add devlink_fmsg_put() macro Mateusz Polchlopek
2024-07-08 12:41 ` Simon Horman
2024-07-03 12:59 ` [Intel-wired-lan] [PATCH iwl-next v1 3/6] ice: add Tx hang devlink health reporter Mateusz Polchlopek
2024-07-05 0:23 ` kernel test robot
2024-07-08 12:40 ` Simon Horman
2024-07-10 13:59 ` Przemek Kitszel
2024-07-03 12:59 ` [Intel-wired-lan] [PATCH iwl-next v1 4/6] ice: print ethtool stats as part of " Mateusz Polchlopek
2024-07-08 12:41 ` Simon Horman
2024-07-03 12:59 ` [Intel-wired-lan] [PATCH iwl-next v1 5/6] ice: Add MDD logging via devlink health Mateusz Polchlopek
2024-07-08 12:42 ` Simon Horman
2024-07-03 12:59 ` [Intel-wired-lan] [PATCH iwl-next v1 6/6] ice: devlink health: dump also skb on Tx hang Mateusz Polchlopek
2024-07-08 12:42 ` Simon Horman
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=20240703125922.5625-1-mateusz.polchlopek@intel.com \
--to=mateusz.polchlopek@intel.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=dwaipayanray1@gmail.com \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=willemb@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®