xe_bo_restore_pinned(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– xe_bo_restore_pinned β€” bestie edition πŸ’–

okay so you're looking at xe_bo_restore_pinned(9) from the Kernel API Manual, and honestly? she's a lil function with one job and she does it. let's get into it 🫢


✨ NAME ✨

xe_bo_restore_pinned β€” the girlypop that restores a pinned VRAM object πŸ’…


✨ SYNOPSIS ✨

int xe_bo_restore_pinned (struct xe_bo *bo );

that's it. that's the whole signature. no cap. πŸŽ€


✨ ARGUMENTS ✨

  • bo β€” the buffer object we're moving. that's the vibe, she's the main character here πŸ‘‘

✨ DESCRIPTION ✨

so like, on successful completion, the object memory will be moved back to VRAM. literally just moved back. slay. ✨

and why do we even need this? because there's special handling for pinned VRAM objects during suspend-resume, and this is the little function that handles it. it's giving "i'm the responsible one in the group chat" energy fr fr 🧚


✨ RETURN ✨

  • 0 on success πŸ˜ŒπŸ’–
  • a negative error code on failure πŸ˜­πŸ’€

✨ SEE ALSO ✨

okay bestie, buckle up, this list is LONG and honestly it ate πŸ‘‘

kernel file ./drivers/gpu/drm/xe/xe_bo.c plus:

like i said. she ate and left no crumbs πŸ“πŸŒˆ


ngl this one's a small page but the see-also is basically a whole friend group πŸ’€ don't skip it, iykyk.

and that's the whole page, bestie! πŸ¦‹ this lil cutie lives in ./drivers/gpu/drm/xe, it's Kernel API Manual business, dated October 2026, and the header says xe_bo_restore_pinned(9) β€” periodt. πŸ’œπŸŽ€

πŸ“¦ where this page comes from