drivers/nvme/target/debugfs.h

File Facts

System

Linux kernel

Corpus path

drivers/nvme/target/debugfs.h

Extension

.h

Size

1044 bytes

Lines

43

Domain

Representative Device Path

Bucket

PCIe NVMe Storage Path

Inferred role

Representative Device Path: implementation source

Status

source implementation candidate

Why This File Exists

Part of the selected hardware vertical slice: PCI discovery, driver binding, NVMe queues, block requests, DMA, interrupts, and completion.

• Part of the selected hardware vertical slice: PCI discovery, driver binding, NVMe queues, block requests, DMA, interrupts, and completion.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/types.h

Detected Declarations

• function nvmet_debugfs_subsys_setup
• function nvmet_debugfs_subsys_free
• function nvmet_debugfs_ctrl_free
• function nvmet_exit_debugfs

Annotated Snippet

static inline void nvmet_debugfs_subsys_free(struct nvmet_subsys *subsys){}

static inline int nvmet_debugfs_ctrl_setup(struct nvmet_ctrl *ctrl)
{
	return 0;
}
static inline void nvmet_debugfs_ctrl_free(struct nvmet_ctrl *ctrl) {}

static inline int __init nvmet_init_debugfs(void)
{
    return 0;
}

static inline void nvmet_exit_debugfs(void) {}

#endif

#endif /* NVMET_DEBUGFS_H */

Annotation

• Immediate include surface: `linux/types.h`.
• Detected declarations: `function nvmet_debugfs_subsys_setup`, `function nvmet_debugfs_subsys_free`, `function nvmet_debugfs_ctrl_free`, `function nvmet_exit_debugfs`.
• Atlas domain: Representative Device Path / PCIe NVMe Storage Path.
• Implementation status: source implementation candidate.

Implementation Notes

• This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
• Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
• Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.