xe_range_fence_tree_next(9)
π xe_range_fence_tree_next β range fence tree iterator next
okay so bestie, welcome to the Kernel API Manual β¨ this one's a lil function called xe_range_fence_tree_next and honestly? it's giving "just give me the next one" energy and we love that for us π
πΈ SYNOPSIS πΈ
struct xe_range_fence * xe_range_fence_tree_next (struct xe_range_fence
*rfence , u64 start , u64 last );
like, literally that's the whole vibe β you hand it a range fence, a start, and a last, and it hands you back a pointer. slay π₯
π ARGUMENTS π
rfenceβ the current range fence π«Ά like, the one you're standing on right now. your main character.startβ start address of range fence β that's the beginning of the range, no cap.lastβ last address of range fence π the end of the range. the finale. the periodt.
β¨ RETURN β¨
next range fence found in range, or NULL π yeah β if there's nothing in the range you get NULL, which is the code equivalent of opening the fridge and finding nothing but vibes π
π¦ SEE ALSO π¦
- Kernel file
./drivers/gpu/drm/xe/xe_range_fence.cβ the source material, iykyk π xe_range_fence_insert(9)xe_range_fence_tree_init(9)xe_range_fence_tree_fini(9)xe_range_fence_tree_first(9)
the whole squad fr fr π§π
ngl this page is short and sweet but every single detail is here β nothing skipped, nothing invented, we just made it cute π
okay bye bestie, go iterate that tree ππ
β mwah, from the ./drivers/gpu/drm/xe girlies, October 2026 edition, xe_range_fence_tree_next(9) π
π¦ 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