drivers/gpu/drm/xe/xe_devcoredump_types.h
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/xe/xe_devcoredump_types.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/xe/xe_devcoredump_types.h- Extension
.h- Size
- 2867 bytes
- Lines
- 94
- 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/ktime.hlinux/mutex.hxe_hw_engine_types.h
Detected Declarations
struct xe_devicestruct xe_gtstruct xe_devcoredump_snapshotstruct xe_devcoredump
Annotated Snippet
struct xe_devcoredump_snapshot {
/** @snapshot_time: Time of this capture. */
ktime_t snapshot_time;
/** @boot_time: Relative boot time so the uptime can be calculated. */
ktime_t boot_time;
/** @process_name: Name of process that triggered this gpu hang */
char process_name[TASK_COMM_LEN];
/** @pid: Process id of process that triggered this gpu hang */
pid_t pid;
/** @reason: The reason the coredump was triggered */
char *reason;
/** @gt: Affected GT, used by forcewake for delayed capture */
struct xe_gt *gt;
/** @work: Workqueue for deferred capture outside of signaling context */
struct work_struct work;
/** @guc: GuC snapshots */
struct {
/** @guc.ct: GuC CT snapshot */
struct xe_guc_ct_snapshot *ct;
/** @guc.log: GuC log snapshot */
struct xe_guc_log_snapshot *log;
} guc;
/** @ge: GuC Submission Engine snapshot */
struct xe_guc_submit_exec_queue_snapshot *ge;
/** @hwe: HW Engine snapshot array */
struct xe_hw_engine_snapshot *hwe[XE_NUM_HW_ENGINES];
/** @job: Snapshot of job state */
struct xe_sched_job_snapshot *job;
/**
* @matched_node: The matched capture node for timedout job
* this single-node tracker works because devcoredump will always only
* produce one hw-engine capture per devcoredump event
*/
struct __guc_capture_parsed_output *matched_node;
/** @vm: Snapshot of VM state */
struct xe_vm_snapshot *vm;
/** @read: devcoredump in human readable format */
struct {
/** @read.size: size of devcoredump in human readable format */
ssize_t size;
/** @read.chunk_position: position of devcoredump chunk */
ssize_t chunk_position;
/** @read.buffer: buffer of devcoredump in human readable format */
char *buffer;
} read;
};
/**
* struct xe_devcoredump - Xe devcoredump main structure
*
* This struct represents the live and active dev_coredump node.
* It is created/populated at the time of a crash/error. Then it
* is read later when user access the device coredump data file
* for reading the information.
*/
struct xe_devcoredump {
/** @lock: protects access to entire structure */
struct mutex lock;
/** @captured: The snapshot of the first hang has already been taken */
bool captured;
/** @snapshot: Snapshot is captured at time of the first crash */
struct xe_devcoredump_snapshot snapshot;
};
#endif
Annotation
- Immediate include surface: `linux/ktime.h`, `linux/mutex.h`, `xe_hw_engine_types.h`.
- Detected declarations: `struct xe_device`, `struct xe_gt`, `struct xe_devcoredump_snapshot`, `struct xe_devcoredump`.
- 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.