From: Rasesh Mody <rmody@marvell.com>
To: <jerinj@marvell.com>, <ferruh.yigit@intel.com>
Cc: Rasesh Mody <rmody@marvell.com>, <dev@dpdk.org>,
<GR-Everest-DPDK-Dev@marvell.com>
Subject: [dpdk-dev] [PATCH v2 0/4] net/qede: add FW debug data collection support
Date: Tue, 30 Jun 2020 01:32:11 -0700 [thread overview]
Message-ID: <20200630083215.13108-1-rmody@marvell.com> (raw)
In-Reply-To: <20200628055850.5275-1-rmody@marvell.com>
Hi Jerin, Ferruh,
This patch-set adds an ability to collect FW and HW Debug Data/Dump
(referred to as FW/HW Dump) to QEDE PMD. The dump is collected either
when PMD detects an error or when a DPDK application asks PMD to
collect it upon detection of application error. This FW/HW Dump
needs to be saved to a file and sent to Marvell for analysis.
Please apply to dpdk-next-net-mrvl and dpdk-next-net trees.
v2:
Addressed checkpatch issues and updated supported features.
Thanks!
-Rasesh
Rasesh Mody (4):
net/qede/base: re-arrange few structures for DDC
net/qede/base: add changes for debug data collection
net/qede: add infrastructure for debug data collection
net/qede: add support for get register operation
doc/guides/nics/features/qede.ini | 1 +
drivers/net/qede/Makefile | 5 +-
drivers/net/qede/base/bcm_osal.c | 31 +
drivers/net/qede/base/bcm_osal.h | 18 +-
drivers/net/qede/base/common_hsi.h | 1 +
drivers/net/qede/base/ecore.h | 54 +-
drivers/net/qede/base/ecore_cxt.c | 200 +-
drivers/net/qede/base/ecore_cxt.h | 140 +-
drivers/net/qede/base/ecore_dev.c | 13 +
drivers/net/qede/base/ecore_hsi_common.h | 184 +-
drivers/net/qede/base/ecore_hsi_debug_tools.h | 2 +-
drivers/net/qede/base/ecore_hsi_func_common.h | 17 +
drivers/net/qede/base/ecore_init_fw_funcs.h | 7 -
drivers/net/qede/base/ecore_mcp.c | 211 +
drivers/net/qede/base/ecore_mcp_api.h | 37 +
drivers/net/qede/base/ecore_status.h | 2 +
drivers/net/qede/base/reg_addr.h | 846 ++
drivers/net/qede/qede_debug.c | 8120 +++++++++++++++++
drivers/net/qede/qede_debug.h | 759 ++
drivers/net/qede/qede_ethdev.c | 2 +-
drivers/net/qede/qede_ethdev.h | 25 +
drivers/net/qede/qede_if.h | 45 +
drivers/net/qede/qede_main.c | 42 +-
drivers/net/qede/qede_regs.c | 271 +
24 files changed, 10874 insertions(+), 159 deletions(-)
create mode 100644 drivers/net/qede/base/ecore_hsi_func_common.h
create mode 100644 drivers/net/qede/qede_debug.c
create mode 100644 drivers/net/qede/qede_debug.h
create mode 100644 drivers/net/qede/qede_regs.c
--
2.18.0
next prev parent reply other threads:[~2020-06-30 8:32 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-28 5:58 [dpdk-dev] [PATCH " Rasesh Mody
2020-06-28 5:58 ` [dpdk-dev] [PATCH 1/4] net/qede/base: re-arrange few structures for DDC Rasesh Mody
2020-06-28 5:58 ` [dpdk-dev] [PATCH 2/4] net/qede/base: add changes for debug data collection Rasesh Mody
2020-06-28 5:58 ` [dpdk-dev] [PATCH 3/4] net/qede: add infrastructure " Rasesh Mody
2020-06-28 12:29 ` Jerin Jacob
2020-06-30 7:38 ` [dpdk-dev] [EXT] " Rasesh Mody
2020-06-28 5:58 ` [dpdk-dev] [PATCH 4/4] net/qede: add support for get register operation Rasesh Mody
2020-06-28 12:23 ` Jerin Jacob
2020-06-30 7:37 ` [dpdk-dev] [EXT] " Rasesh Mody
2020-06-30 8:32 ` Rasesh Mody [this message]
2020-07-07 20:18 ` [dpdk-dev] [PATCH v3 0/4] net/qede: add FW debug data collection support Rasesh Mody
2020-07-07 21:16 ` [dpdk-dev] [PATCH v4 " Rasesh Mody
2020-07-08 22:50 ` [dpdk-dev] [PATCH v5 " Rasesh Mody
2020-07-08 22:50 ` [dpdk-dev] [PATCH v5 1/4] net/qede/base: re-arrange few structures for DDC Rasesh Mody
2020-07-08 22:50 ` [dpdk-dev] [PATCH v5 2/4] net/qede/base: add changes for debug data collection Rasesh Mody
2020-07-08 22:50 ` [dpdk-dev] [PATCH v5 3/4] net/qede: add infrastructure " Rasesh Mody
2020-07-09 16:37 ` Ferruh Yigit
2020-07-09 23:30 ` [dpdk-dev] [EXT] " Rasesh Mody
2020-07-08 22:50 ` [dpdk-dev] [PATCH v5 4/4] net/qede: add support for get register operation Rasesh Mody
2020-07-09 10:11 ` Jerin Jacob
2020-07-09 16:32 ` Ferruh Yigit
2020-07-09 23:30 ` [dpdk-dev] [EXT] " Rasesh Mody
2020-07-07 21:16 ` [dpdk-dev] [PATCH v4 1/4] net/qede/base: re-arrange few structures for DDC Rasesh Mody
2020-07-07 21:16 ` [dpdk-dev] [PATCH v4 2/4] net/qede/base: add changes for debug data collection Rasesh Mody
2020-07-07 21:16 ` [dpdk-dev] [PATCH v4 3/4] net/qede: add infrastructure " Rasesh Mody
2020-07-07 21:16 ` [dpdk-dev] [PATCH v4 4/4] net/qede: add support for get register operation Rasesh Mody
2020-07-08 9:29 ` Jerin Jacob
2020-07-07 20:18 ` [dpdk-dev] [PATCH v3 1/4] net/qede/base: re-arrange few structures for DDC Rasesh Mody
2020-07-07 20:18 ` [dpdk-dev] [PATCH v3 2/4] net/qede/base: add changes for debug data collection Rasesh Mody
2020-07-07 20:18 ` [dpdk-dev] [PATCH v3 3/4] net/qede: add infrastructure " Rasesh Mody
2020-07-07 20:18 ` [dpdk-dev] [PATCH v3 4/4] net/qede: add support for get register operation Rasesh Mody
2020-06-30 8:32 ` [dpdk-dev] [PATCH v2 1/4] net/qede/base: re-arrange few structures for DDC Rasesh Mody
2020-06-30 17:47 ` Jerin Jacob
2020-07-07 21:20 ` [dpdk-dev] [EXT] " Rasesh Mody
2020-06-30 8:32 ` [dpdk-dev] [PATCH v2 2/4] net/qede/base: add changes for debug data collection Rasesh Mody
2020-06-30 8:32 ` [dpdk-dev] [PATCH v2 3/4] net/qede: add infrastructure " Rasesh Mody
2020-06-30 8:32 ` [dpdk-dev] [PATCH v2 4/4] net/qede: add support for get register operation Rasesh Mody
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=20200630083215.13108-1-rmody@marvell.com \
--to=rmody@marvell.com \
--cc=GR-Everest-DPDK-Dev@marvell.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinj@marvell.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;
as well as URLs for NNTP newsgroup(s).