From: Simon Horman <simon.horman@netronome.com>
To: David Miller <davem@davemloft.net>,
Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: netdev@vger.kernel.org, oss-drivers@netronome.com,
Carl Heymann <carl.heymann@netronome.com>,
Simon Horman <simon.horman@netronome.com>
Subject: [PATCH net-next 00/10] nfp: enhanced debug dump via ethtool
Date: Mon, 4 Dec 2017 23:34:11 +0100 [thread overview]
Message-ID: <20171204223421.19174-1-simon.horman@netronome.com> (raw)
Add debug dump implementation to the NFP driver. This makes use of
existing ethtool infrastructure. ethtool -W is used to select the dump
level and ethtool -w is used to dump NFP state.
The existing behaviour of dump level 0, dumping the arm.diag resource, is
preserved. Dump levels greater than 0 are implemented by this patchset and
optionally supported by firmware providing a _abi_dump_spec rtsym. This
rtsym provides a specification, in TLV format, of the information to be
dumped from the NFP at each supported dump level.
Dumps are also structured using a TLVs. They consist a prolog and the data
described int he corresponding dump.
Carl Heymann (10):
nfp: debug dump ethtool ops
nfp: load debug dump spec
nfp: dump prolog
nfp: dumpspec TLV traversal
nfp: dump rtsyms
nfp: dump all hwinfo
nfp: dump single hwinfo field by key
nfp: dump firmware name
nfp: dump CPP, XPB and direct ME CSRs
nfp: dump indirect ME CSRs
drivers/net/ethernet/netronome/nfp/Makefile | 1 +
drivers/net/ethernet/netronome/nfp/nfp_asm.h | 10 +
drivers/net/ethernet/netronome/nfp/nfp_main.c | 6 +
drivers/net/ethernet/netronome/nfp/nfp_main.h | 29 +
.../net/ethernet/netronome/nfp/nfp_net_debugdump.c | 787 +++++++++++++++++++++
.../net/ethernet/netronome/nfp/nfp_net_ethtool.c | 55 +-
drivers/net/ethernet/netronome/nfp/nfpcore/nfp.h | 2 +
.../ethernet/netronome/nfp/nfpcore/nfp_hwinfo.c | 10 +
8 files changed, 892 insertions(+), 8 deletions(-)
create mode 100644 drivers/net/ethernet/netronome/nfp/nfp_net_debugdump.c
--
2.11.0
next reply other threads:[~2017-12-04 22:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 22:34 Simon Horman [this message]
2017-12-04 22:34 ` [PATCH net-next 01/10] nfp: debug dump ethtool ops Simon Horman
2017-12-04 22:34 ` [PATCH net-next 02/10] nfp: load debug dump spec Simon Horman
2017-12-04 22:34 ` [PATCH net-next 03/10] nfp: dump prolog Simon Horman
2017-12-04 22:34 ` [PATCH net-next 04/10] nfp: dumpspec TLV traversal Simon Horman
2017-12-04 22:34 ` [PATCH net-next 05/10] nfp: dump rtsyms Simon Horman
2017-12-04 22:34 ` [PATCH net-next 06/10] nfp: dump all hwinfo Simon Horman
2017-12-04 22:34 ` [PATCH net-next 07/10] nfp: dump single hwinfo field by key Simon Horman
2017-12-04 22:34 ` [PATCH net-next 08/10] nfp: dump firmware name Simon Horman
2017-12-04 22:34 ` [PATCH net-next 09/10] nfp: dump CPP, XPB and direct ME CSRs Simon Horman
2017-12-04 22:34 ` [PATCH net-next 10/10] nfp: dump indirect " Simon Horman
2017-12-05 20:01 ` [PATCH net-next 00/10] nfp: enhanced debug dump via ethtool 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=20171204223421.19174-1-simon.horman@netronome.com \
--to=simon.horman@netronome.com \
--cc=carl.heymann@netronome.com \
--cc=davem@davemloft.net \
--cc=jakub.kicinski@netronome.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.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).