xe_bo_sg_is_contiguous(9)
π xe_bo_sg_is_contiguous(9) π
okay so this is a page from the Kernel API Manual bestie, and it's literally all about xe_bo_sg_is_contiguous β the tiny little helper that does a vibe check on your BO's DMA address space π¦
β¨ NAME β¨
xe_bo_sg_is_contiguous β check if a BO's DMA address space is contiguous, no cap π₯
π SYNOPSIS π
bool xe_bo_sg_is_contiguous (struct xe_bo *bo , size_t len );
it's giving "one function, two arguments, one bool," and honestly? iconic π
πΈ ARGUMENTS πΈ
boβ the BO you wanna check π it must have a valid sg table, i.e.!xe_bo_is_vramβ so like, if that's not your situation, this is not the function for you bestie, read the room πlenβ the required contiguous length in bytes π like how much of it you actually need to be one big happy contiguous chunk
π DESCRIPTION π
returns true if the first len bytes of the BO are mapped to a contiguous DMA address range β¨
that's it. that's the whole lore. it checks, it returns a bool, it slays π«Ά
π§ SEE ALSO π§
kernel file ./drivers/gpu/drm/xe/xe_bo.h enum β¨ plus the whole friend group:
xe_madv_purgeable_state(9)xe_bo_is_purged(9)xe_bo_madv_is_dontneed(9)xe_bo_willneed_get_locked(9)xe_bo_willneed_put_locked(9)xe_bo_vma_count_inc_locked(9)xe_bo_vma_count_dec_locked(9)xe_bo_size(9)xe_bo_has_valid_ccs_bb(9)xe_bo_put_deferred(9)xe_bo_put_async(9)struct xe_bo_shrink_flags(9)xe_bo_is_mem_type(9)
like, the entire squad shows up. main character energy all around ππ
π reminder:bohas to have a valid sg table (!xe_bo_is_vram) β don't come at this function with a VRAM BO and expect contiguity tea, it's not built for that π
that's the page!! brought to you by ./drivers/gpu/drm/xe, October 2026 edition, xe_bo_sg_is_contiguous(9) β periodt π
βπ
π¦ 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