From: Hannes Reinecke <hare@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Sagi Grimberg <sagi@grimberg.me>, Keith Busch <kbusch@kernel.org>,
linux-nvme@lists.infradead.org, Hannes Reinecke <hare@kernel.org>
Subject: [PATCHv3 0/8] nvmet: debugfs support
Date: Fri, 22 Mar 2024 08:03:25 +0100 [thread overview]
Message-ID: <20240322070333.3820-1-hare@kernel.org> (raw)
Hi all,
taking up the original patchset for nvmet debugfs
I've improved upon that submission by modifying
the layout:
/dev/kernel/debug/nvmet
<subsysnqn>
ctrl<cntlid>
port
state
hostnqn
kato
host_traddr
queue<qnum>
sqsize
sqhead
The 'state' attribute is the value of the
CSTS register; one can trigger a controller reset
by writing 'fatal' into it (to set CSTS.CFS).
As usual, comments and reviews are welcome.
Changes to v2:
- Move the 'host_traddr' attribute to the
controller directory
- Rename callback to 'host_traddr'
Hannes Reinecke (8):
nvmet: add debugfs support
nvmet: add 'host_traddr' callback for debugfs
nvmet-tcp: implement host_traddr()
nvmet-rdma: implement host_traddr()
nvmet-fc: implement host_traddr()
nvme-fcloop: implement 'host_traddr'
lpfc_nvmet: implement 'host_traddr'
nvmet: add debugfs support for queues
drivers/nvme/target/Kconfig | 9 ++
drivers/nvme/target/Makefile | 1 +
drivers/nvme/target/core.c | 32 ++++-
drivers/nvme/target/debugfs.c | 250 +++++++++++++++++++++++++++++++++
drivers/nvme/target/debugfs.h | 50 +++++++
drivers/nvme/target/fc.c | 33 +++++
drivers/nvme/target/fcloop.c | 11 ++
drivers/nvme/target/nvmet.h | 15 +-
drivers/nvme/target/rdma.c | 12 ++
drivers/nvme/target/tcp.c | 14 ++
drivers/scsi/lpfc/lpfc_nvmet.c | 11 ++
include/linux/nvme-fc-driver.h | 4 +
12 files changed, 439 insertions(+), 3 deletions(-)
create mode 100644 drivers/nvme/target/debugfs.c
create mode 100644 drivers/nvme/target/debugfs.h
--
2.35.3
next reply other threads:[~2024-03-22 7:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 7:03 Hannes Reinecke [this message]
2024-03-22 7:03 ` [PATCH 1/8] nvmet: add debugfs support Hannes Reinecke
2024-03-23 20:25 ` Sagi Grimberg
2024-03-26 11:55 ` Hannes Reinecke
2024-03-25 18:18 ` Daniel Wagner
2024-03-25 19:22 ` Daniel Wagner
2024-03-25 22:39 ` Sagi Grimberg
2024-03-26 7:16 ` Daniel Wagner
2024-03-26 7:14 ` Hannes Reinecke
2024-03-26 7:22 ` Daniel Wagner
2024-03-22 7:03 ` [PATCH 2/8] nvmet: add 'host_traddr' callback for debugfs Hannes Reinecke
2024-03-23 20:27 ` Sagi Grimberg
2024-03-22 7:03 ` [PATCH 3/8] nvmet-tcp: implement host_traddr() Hannes Reinecke
2024-03-23 20:27 ` Sagi Grimberg
2024-03-22 7:03 ` [PATCH 4/8] nvmet-rdma: " Hannes Reinecke
2024-03-23 20:27 ` Sagi Grimberg
2024-03-22 7:03 ` [PATCH 5/8] nvmet-fc: " Hannes Reinecke
2024-03-22 7:03 ` [PATCH 6/8] nvme-fcloop: implement 'host_traddr' Hannes Reinecke
2024-03-22 7:03 ` [PATCH 7/8] lpfc_nvmet: " Hannes Reinecke
2024-03-22 7:03 ` [PATCH 8/8] nvmet: add debugfs support for queues Hannes Reinecke
2024-03-23 20:31 ` Sagi Grimberg
2024-03-25 7:25 ` Hannes Reinecke
2024-03-25 9:07 ` Sagi Grimberg
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=20240322070333.3820-1-hare@kernel.org \
--to=hare@kernel.org \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).