drivers/gpu/drm/xe/xe_sriov_vf_ccs_types.h
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/xe/xe_sriov_vf_ccs_types.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/xe/xe_sriov_vf_ccs_types.h- Extension
.h- Size
- 1133 bytes
- Lines
- 49
- 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/types.h
Detected Declarations
struct xe_sriov_vf_ccs_ctxstruct xe_sriov_vf_ccsenum xe_sriov_vf_ccs_rw_ctxs
Annotated Snippet
struct xe_sriov_vf_ccs_ctx {
/** @ctx_id: Id to which context it belongs to */
enum xe_sriov_vf_ccs_rw_ctxs ctx_id;
/** @mig_q: exec queues used for migration */
struct xe_exec_queue *mig_q;
/** @mem: memory data */
struct {
/** @mem.ccs_bb_pool: Pool from which batch buffers are allocated. */
struct xe_mem_pool *ccs_bb_pool;
} mem;
};
/**
* struct xe_sriov_vf_ccs - The VF CCS migration support data.
*/
struct xe_sriov_vf_ccs {
/** @contexts: CCS read and write contexts for VF. */
struct xe_sriov_vf_ccs_ctx contexts[XE_SRIOV_VF_CCS_CTX_COUNT];
/** @initialized: Initialization of VF CCS is completed or not. */
bool initialized;
};
#endif
Annotation
- Immediate include surface: `linux/types.h`.
- Detected declarations: `struct xe_sriov_vf_ccs_ctx`, `struct xe_sriov_vf_ccs`, `enum xe_sriov_vf_ccs_rw_ctxs`.
- 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.