drivers/gpu/drm/i915/selftests/igt_flush_test.c
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/i915/selftests/igt_flush_test.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/i915/selftests/igt_flush_test.c- Extension
.c- Size
- 1043 bytes
- Lines
- 52
- 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
gt/intel_gt.hgt/intel_gt_requests.hi915_drv.hi915_selftest.higt_flush_test.h
Detected Declarations
function igt_flush_testfunction for_each_gtfunction for_each_engine
Annotated Snippet
for_each_engine(engine, gt, id) {
if (engine->props.preempt_timeout_ms > timeout_ms)
timeout_ms = engine->props.preempt_timeout_ms;
}
cond_resched();
/* 2x longest preempt timeout, experimentally determined */
if (intel_gt_wait_for_idle(gt, HZ * timeout_ms / 500) == -ETIME) {
pr_err("%pS timed out, cancelling all further testing.\n",
__builtin_return_address(0));
GEM_TRACE("%pS timed out.\n",
__builtin_return_address(0));
GEM_TRACE_DUMP();
intel_gt_set_wedged(gt);
ret = -EIO;
}
}
return ret;
}
Annotation
- Immediate include surface: `gt/intel_gt.h`, `gt/intel_gt_requests.h`, `i915_drv.h`, `i915_selftest.h`, `igt_flush_test.h`.
- Detected declarations: `function igt_flush_test`, `function for_each_gt`, `function for_each_engine`.
- 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.