xe_bo_sg_is_contiguous(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– 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:

like, the entire squad shows up. main character energy all around πŸ˜­πŸ’–


🌈 reminder: bo has 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