xe_bo_notif...epare_pinned(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… xe_bo_notifier_prepare_pinned β€” Kernel API Manual πŸŽ€

okay so bestie, welcome to the Kernel API Manual entry for xe_bo_notifier_prepare_pinned ✨ (the header up top truncates it as xe_bo_notif...epare_pinned(9) which is honestly giving "my name got cut off in the group chat preview" 😭 but we know her full name now).


🌸 NAME 🌸

xe_bo_notifier_prepare_pinned β€” get a pinned VRAM object ready to be backed up in system memory 🫢


✨ SYNOPSIS ✨

int xe_bo_notifier_prepare_pinned (struct xe_bo *bo );

literally one argument, one int, no drama πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • bo β€” the buffer object we're prepping. that's her. the main character of this function πŸŽ€

πŸ’– DESCRIPTION πŸ’–

so here's the vibe: if this call succeeds, the object's backup pages get allocated, periodt ✨ Expectation is that you're calling this from the PM notifier, before suspend/hibernation kicks in 😴 β€” like packing your bag the night before, not while the car's already pulling out of the driveway πŸš—πŸ’¨


πŸ”₯ RETURN πŸ”₯

  • 0 on success πŸŽ‰
  • a negative error code on failure πŸ’€ (no cap, check it)

πŸ‘‘ SEE ALSO πŸ‘‘

the whole friend group, in the kernel file ./drivers/gpu/drm/xe/xe_bo.c:


and that's the whole thing, bestie β€” you ate πŸ’…βœ¨

this legend lives in ./drivers/gpu/drm/xe, dated October 2026, and yes the page still signs off as xe_bo_notif...epare_pinned(9) because she refuses to change her display name 😭🫢

πŸ“¦ where this page comes from