From: <edward.cree@amd.com>
To: <linux-net-drivers@amd.com>, <davem@davemloft.net>,
<kuba@kernel.org>, <pabeni@redhat.com>, <edumazet@google.com>
Cc: Edward Cree <ecree.xilinx@gmail.com>, <netdev@vger.kernel.org>,
<habetsm.xilinx@gmail.com>
Subject: [PATCH net-next 0/7] sfc: initial debugfs support
Date: Mon, 11 Dec 2023 17:18:25 +0000 [thread overview]
Message-ID: <cover.1702314694.git.ecree.xilinx@gmail.com> (raw)
From: Edward Cree <ecree.xilinx@gmail.com>
Expose some basic information about the NIC, its channels and queues
and their assignments.
Edward Cree (7):
sfc: initial debugfs implementation
sfc: debugfs for channels
sfc: debugfs for (nic) RX queues
sfc: debugfs for (nic) TX queues
sfc: add debugfs nodes for loopback mode
sfc: add debugfs entries for filter table status
sfc: add debugfs node for filter table contents
drivers/net/ethernet/sfc/Makefile | 1 +
drivers/net/ethernet/sfc/debugfs.c | 539 ++++++++++++++++++++++++
drivers/net/ethernet/sfc/debugfs.h | 149 +++++++
drivers/net/ethernet/sfc/ef10.c | 10 +
drivers/net/ethernet/sfc/ef100_netdev.c | 7 +
drivers/net/ethernet/sfc/ef100_nic.c | 8 +
drivers/net/ethernet/sfc/efx.c | 15 +-
drivers/net/ethernet/sfc/efx_channels.c | 8 +
drivers/net/ethernet/sfc/efx_common.c | 7 +
drivers/net/ethernet/sfc/mcdi_filters.c | 57 +++
drivers/net/ethernet/sfc/mcdi_filters.h | 4 +
drivers/net/ethernet/sfc/net_driver.h | 47 +++
drivers/net/ethernet/sfc/rx_common.c | 9 +
drivers/net/ethernet/sfc/tx_common.c | 8 +
14 files changed, 868 insertions(+), 1 deletion(-)
create mode 100644 drivers/net/ethernet/sfc/debugfs.c
create mode 100644 drivers/net/ethernet/sfc/debugfs.h
next reply other threads:[~2023-12-11 17:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 17:18 edward.cree [this message]
2023-12-11 17:18 ` [PATCH net-next 1/7] sfc: initial debugfs implementation edward.cree
2023-12-15 0:05 ` Nelson, Shannon
2024-02-08 21:25 ` Edward Cree
2023-12-11 17:18 ` [PATCH net-next 2/7] sfc: debugfs for channels edward.cree
2023-12-12 19:54 ` kernel test robot
2023-12-11 17:18 ` [PATCH net-next 3/7] sfc: debugfs for (nic) RX queues edward.cree
2023-12-12 22:06 ` kernel test robot
2023-12-15 0:05 ` Nelson, Shannon
2025-02-14 15:51 ` Edward Cree
2025-02-14 17:39 ` Nelson, Shannon
2023-12-11 17:18 ` [PATCH net-next 4/7] sfc: debugfs for (nic) TX queues edward.cree
2023-12-13 0:15 ` kernel test robot
2023-12-11 17:18 ` [PATCH net-next 5/7] sfc: add debugfs nodes for loopback mode edward.cree
2023-12-11 17:18 ` [PATCH net-next 6/7] sfc: add debugfs entries for filter table status edward.cree
2023-12-11 19:25 ` Simon Horman
2023-12-15 0:05 ` Nelson, Shannon
2025-02-14 16:23 ` Edward Cree
2025-02-14 17:47 ` Nelson, Shannon
2023-12-11 17:18 ` [PATCH net-next 7/7] sfc: add debugfs node for filter table contents edward.cree
2023-12-11 19:17 ` Simon Horman
2023-12-12 13:58 ` Edward Cree
2023-12-12 15:14 ` Edward Cree
2023-12-12 16:19 ` Jakub Kicinski
2023-12-13 12:15 ` Edward Cree
2023-12-14 16:56 ` Simon Horman
2023-12-15 0:05 ` Nelson, Shannon
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=cover.1702314694.git.ecree.xilinx@gmail.com \
--to=edward.cree@amd.com \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=habetsm.xilinx@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-net-drivers@amd.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 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).