drivers/gpu/drm/xe/xe_guc_relay_types.h
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/xe/xe_guc_relay_types.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/xe/xe_guc_relay_types.h- Extension
.h- Size
- 1016 bytes
- Lines
- 41
- 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
linux/mempool.hlinux/ratelimit_types.hlinux/spinlock.hlinux/workqueue.h
Detected Declarations
struct xe_guc_relay
Annotated Snippet
struct xe_guc_relay {
/** @lock: protects all internal data. */
spinlock_t lock;
/** @worker: dispatches incoming action messages. */
struct work_struct worker;
/** @pending_relays: list of sent requests that await a response. */
struct list_head pending_relays;
/** @incoming_actions: list of incoming relay action messages to process. */
struct list_head incoming_actions;
/** @pool: pool of the relay message buffers. */
mempool_t pool;
/** @last_rid: last Relay-ID used while sending a message. */
u32 last_rid;
/** @diag_ratelimit: ratelimit state used to throttle diagnostics messages. */
struct ratelimit_state diag_ratelimit;
};
#endif
Annotation
- Immediate include surface: `linux/mempool.h`, `linux/ratelimit_types.h`, `linux/spinlock.h`, `linux/workqueue.h`.
- Detected declarations: `struct xe_guc_relay`.
- 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.