xe_ggtt_remove_bo(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… xe_ggtt_remove_bo(9) β€” the kernel API manual, but make it cute

okay so this is xe_ggtt_remove_bo, bestie, and it lives in the Kernel API Manual, section 9 β€” you know, the section where all the good kernel-internals lore hangs out. This one does exactly one thing and honestly it ate: it removes a BO from the GGTT. That's it. That's the whole vibe. ✨


🌸 NAME 🌸

xe_ggtt_remove_bo β€” Remove a BO from the GGTT</p> πŸ’–

Like, literally the title tells you everything, no cap.


πŸŽ€ SYNOPSIS πŸŽ€

void xe_ggtt_remove_bo (struct xe_ggtt *ggtt , struct xe_bo *bo );

notice how it returns void? it's giving "i do my job and i don't report back". main character energy fr fr 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

  • ggtt β€” the xe_ggtt where the node is gonna get removed πŸ‘‹ that's the address-space-bestie in question
  • bo β€” the xe_bo that's getting removed πŸŽ€ so long, buffer object, we hardly knew ye
ngl both of these are pointers and both of them matter. don't be out here passing the wrong one, i'm begging πŸ™ˆ

🌈 SEE ALSO 🌈

okay this list is long and i'm obsessed β€” it's basically the whole GGTT friend group, everyone showed up to the group chat:

like, every single one of them. iykyk πŸ§šβ€β™€οΈ


lowkey important: this page only documents what's written here, so if you need the deep lore on how nodes get inserted, mapped, shifted, dumped, or turned into PTEs β€” that's what the SEE ALSO squad is for. go read them, bestie, they're iconic. πŸ“

mwah πŸ’œ that's the whole page β€” brought to you straight from the ./drivers/gpu/drm/xe directory, dated October 2026, and this little rewrite is xe_ggtt_remove_bo(9) signing off. slay, stay mapped, and remember: remove responsibly βœ¨πŸŽ€

πŸ“¦ where this page comes from