xe_gt_topolo..._in_quadrant(9)
π xe_gt_topology_has_dss_in_quadrant(9) β from the Kernel API Manual, bestie β¨
okay so real talk, this is xe_gt_topology_has_dss_in_quadrant from the Kernel API Manual and she is lowkey iconic for how much she knows about your GPU's fusing πΈ
π NAME π
xe_gt_topology_has_dss_in_quadrant β the vibe check for DSS fusing in a GT quadrant, fr fr π
π¦ SYNOPSIS π¦
bool xe_gt_topology_has_dss_in_quadrant (struct xe_gt *gt , int quad );
β¨ ARGUMENTS β¨
gtβ the GT you want to check, periodt. this is the main character of the call πquadβ which quadrant of the DSS space you're snooping on π
π DESCRIPTION π
so here's the lore π«Ά Since Xe_HP platforms can have up to four CCS engines, those engines are each logically associated with a quarter of the possible DSS. it's giving assigned seating, honestly.
and the way that this matters: if there are no DSS present in one of the four quadrants of the DSS space, the corresponding CCS engine is also not available for use. no DSS, no engine, that's the rule π
so this function returns false if all DSS in a quadrant of the GT are fused off β otherwise it's true. simple as π
ngl if you're getting false back, that quadrant is empty-empty and that CCS engine is not coming to the party π
π₯ SEE ALSO π₯
- Kernel file
./drivers/gpu/drm/xe/xe_gt_topology.cβ go read the source, bestie, iykyk β gen_l3_mask_from_pattern(9)xe_gt_topology_dump(9)β the one that dumps it all out for you π§
and that's the whole page, no cap π this lil writeup lives in ./drivers/gpu/drm/xe, dated October 2026, and the page itself is xe_gt_topolo..._in_quadrant(9) β slay, go check your quadrants ππ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms