From: Lei Chen <lei.chen@smartx.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
Lei Chen <lei.chen@smartx.com>
Subject: [PATCH v2 4/5] scsi: megaraid_sas: Link tag set debugfs to the controller
Date: Fri, 20 Nov 2026 10:56:03 +0800 [thread overview]
Message-ID: <ebe08c3f48026d81fe2af55d5ce8f4743d0c4a39.1795143228.git.lei.chen@smartx.com> (raw)
In-Reply-To: <cover.1795143228.git.lei.chen@smartx.com>
The tag set debugfs directory lists the adapter's request queues, but
does not link to the adapter debugfs entries containing its RAID map.
Link the SCSI host tag set to the megaraid_sas/scsi_host<host-no>
debugfs directory after the Fusion adapter debugfs setup succeeds.
Remove the controller link before deleting the adapter directory.
Signed-off-by: Lei Chen <lei.chen@smartx.com>
---
drivers/scsi/megaraid/megaraid_sas_debugfs.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/scsi/megaraid/megaraid_sas_debugfs.c b/drivers/scsi/megaraid/megaraid_sas_debugfs.c
index 81698cd83f5a..12c582e29ea4 100644
--- a/drivers/scsi/megaraid/megaraid_sas_debugfs.c
+++ b/drivers/scsi/megaraid/megaraid_sas_debugfs.c
@@ -150,6 +150,8 @@ megasas_setup_debugfs(struct megasas_instance *instance)
debugfs_remove(instance->debugfs_root);
return;
}
+ blk_mq_tagset_debugfs_link_controller(&instance->host->tag_set,
+ instance->debugfs_root);
}
}
@@ -160,6 +162,7 @@ megasas_setup_debugfs(struct megasas_instance *instance)
*/
void megasas_destroy_debugfs(struct megasas_instance *instance)
{
+ blk_mq_tagset_debugfs_unlink_controller(&instance->host->tag_set);
debugfs_remove_recursive(instance->debugfs_root);
}
--
2.43.0
next prev parent reply other threads:[~2026-11-20 2:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 3:01 [PATCH v1 0/4] Expose blk-mq tag sets through debugfs Lei Chen
2026-10-09 3:01 ` [PATCH v1 1/4] blk-mq: remove stale comment about non-present CPU mapping Lei Chen
2026-10-09 3:01 ` [PATCH v1 2/4] blk-mq: manage driver tags at the tag set level Lei Chen
2026-10-09 3:01 ` [PATCH v1 3/4] block: expose blk-mq tag sets through debugfs Lei Chen
2026-10-09 3:01 ` [PATCH v1 4/4] block: link request queue debugfs directories to tag sets Lei Chen
2026-11-03 9:04 ` [PATCH v1 0/4] Expose blk-mq tag sets through debugfs Lei Chen
2026-11-20 2:55 ` [PATCH v2 0/5] " Lei Chen
2026-11-20 2:56 ` [PATCH v2 1/5] block: expose " Lei Chen
2026-11-20 2:56 ` [PATCH v2 2/5] block: link request queue debugfs directories to tag sets Lei Chen
2026-11-20 2:56 ` [PATCH v2 3/5] block: add helpers to link tag set debugfs to controllers Lei Chen
2026-11-20 2:56 ` Lei Chen [this message]
2026-11-20 2:56 ` [PATCH v2 5/5] scsi: mpt3sas: Link tag set debugfs to the controller Lei Chen
2026-11-20 2:58 ` [RESEND PATCH v1 0/4] Expose blk-mq tag sets through debugfs Lei Chen
2026-11-20 2:58 ` [RESEND PATCH v1 1/4] blk-mq: remove stale comment about non-present CPU mapping Lei Chen
2026-11-20 2:58 ` [RESEND PATCH v1 2/4] blk-mq: manage driver tags at the tag set level Lei Chen
2026-11-20 2:58 ` [RESEND PATCH v1 3/4] block: expose blk-mq tag sets through debugfs Lei Chen
2026-11-20 2:58 ` [RESEND PATCH v1 4/4] block: link request queue debugfs directories to tag sets Lei Chen
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=ebe08c3f48026d81fe2af55d5ce8f4743d0c4a39.1795143228.git.lei.chen@smartx.com \
--to=lei.chen@smartx.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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®