block/blk-pm.h

File Facts

System

Linux kernel

Corpus path

block/blk-pm.h

Extension

.h

Size

763 bytes

Lines

36

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/pm_runtime.h

Detected Declarations

• function blk_pm_resume_queue
• function blk_pm_mark_last_busy
• function blk_pm_resume_queue
• function blk_pm_mark_last_busy

Annotated Snippet

#ifndef _BLOCK_BLK_PM_H_
#define _BLOCK_BLK_PM_H_

#include <linux/pm_runtime.h>

#ifdef CONFIG_PM
static inline int blk_pm_resume_queue(const bool pm, struct request_queue *q)
{
	if (!q->dev || !blk_queue_pm_only(q))
		return 1;	/* Nothing to do */
	if (pm && q->rpm_status != RPM_SUSPENDED)
		return 1;	/* Request allowed */
	pm_request_resume(q->dev);
	return 0;
}

static inline void blk_pm_mark_last_busy(struct request *rq)
{
	if (rq->q->dev && !(rq->rq_flags & RQF_PM))
		pm_runtime_mark_last_busy(rq->q->dev);
}
#else
static inline int blk_pm_resume_queue(const bool pm, struct request_queue *q)
{
	return 1;
}

static inline void blk_pm_mark_last_busy(struct request *rq)
{
}
#endif

#endif /* _BLOCK_BLK_PM_H_ */

Annotation

• Immediate include surface: `linux/pm_runtime.h`.
• Detected declarations: `function blk_pm_resume_queue`, `function blk_pm_mark_last_busy`, `function blk_pm_resume_queue`, `function blk_pm_mark_last_busy`.
• 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.