drivers/gpu/drm/amd/ras/rascore/ras_process.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/amd/ras/rascore/ras_process.h

Extension

.h

Size

1907 bytes

Lines

54

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• No C-style include directives detected by the generator.

Detected Declarations

• struct ras_event_req
• struct ras_process
• struct ras_core_context

Annotated Snippet

struct ras_event_req {
	uint64_t seqno;
	uint32_t idx_vf;
	uint32_t block;
	uint16_t pasid;
	uint32_t reset;
	void *pasid_fn;
	void *data;
};

struct ras_process {
	void *dev;
	void *ras_process_thread;
	wait_queue_head_t ras_process_wq;
	atomic_t ras_interrupt_req;
	atomic_t umc_interrupt_count;
	struct kfifo event_fifo;
	spinlock_t fifo_spinlock;
};

struct ras_core_context;
int ras_process_init(struct ras_core_context *ras_core);
int ras_process_fini(struct ras_core_context *ras_core);
int ras_process_handle_ras_event(struct ras_core_context *ras_core);
int ras_process_add_interrupt_req(struct ras_core_context *ras_core,
		struct ras_event_req *req, bool is_umc);
#endif

Annotation

• Detected declarations: `struct ras_event_req`, `struct ras_process`, `struct ras_core_context`.
• Atlas domain: Driver Families / drivers/gpu.
• Implementation status: source implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.