drivers/gpu/drm/amd/ras/ras_mgr/amdgpu_ras_cmd.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/amd/ras/ras_mgr/amdgpu_ras_cmd.h

Extension

.h

Size

1896 bytes

Lines

55

Domain

Driver Families

Bucket

drivers/gpu

Inferred role

Driver Families: implementation source

Status

source implementation candidate

Why This File Exists

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

• Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• ras.h

Detected Declarations

• struct ras_cmd_translate_memory_fd_req
• struct ras_cmd_translate_memory_fd_rsp
• enum amdgpu_ras_cmd_id

Annotated Snippet

struct ras_cmd_translate_memory_fd_req {
	struct ras_cmd_dev_handle dev;
	uint32_t type;
	uint32_t fd;
	uint64_t address;
	uint32_t reserved[4];
};

struct ras_cmd_translate_memory_fd_rsp {
	uint32_t version;
	uint32_t padding;
	uint64_t start;
	uint64_t size;
	uint32_t reserved[2];
};

int amdgpu_ras_handle_cmd(struct ras_core_context *ras_core,
		struct ras_cmd_ctx *cmd, void *data);
int amdgpu_ras_submit_cmd(struct ras_core_context *ras_core, struct ras_cmd_ctx *cmd);

#endif

Annotation

• Immediate include surface: `ras.h`.
• Detected declarations: `struct ras_cmd_translate_memory_fd_req`, `struct ras_cmd_translate_memory_fd_rsp`, `enum amdgpu_ras_cmd_id`.
• Atlas domain: Driver Families / drivers/gpu.
• 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.