xe_bo_evict_pinned(9)

📦 version 7.3.1, in nixpkgs unstable

💅 xe_bo_evict_pinned(9) — the Kernel API Manual, bestie edition 🎀

okay so real talk, this is a page from the Kernel API Manual (yes, the xe_bo_evict_pinned(9) one, iykyk) and it's honestly iconic. it's a little function with one job and it does it. let's get into it ✨

🌸 NAME 🌸

xe_bo_evict_pinned — evict a pinned VRAM object to system memory, no cap 🫶

✨ SYNOPSIS ✨

int xe_bo_evict_pinned (struct xe_bo *bo );

that's it. that's the whole signature. slay 💅

🦋 ARGUMENTS 🦋

  • bo — the buffer object to move. literally just the bo that's getting relocated, that's the whole vibe 🎀

💖 DESCRIPTION 💖

so when this call finishes successfully, the object's memory has been moved over to system memory. periodt. 💀

and why do we even need this? because pinned VRAM objects need special handling during suspend-resume 🔥 like, they get their own little moment, and this function is it. main character energy fr fr.

👑 RETURN 👑

  • 0 on success 🌈
  • a negative error code on failure 😭

💜 SEE ALSO 💜

ngl, this is the part where the whole friend group shows up 💅 — the kernel file is ./drivers/gpu/drm/xe/xe_bo.c and here's every single one of its besties:

💀 gentle reminder bestie: read the whole list, there's like forty of them and every single one matters. don't skip. 🫶

okay that's the page!! this one came from ./drivers/gpu/drm/xe, dated October 2026, and it's filed under xe_bo_evict_pinned(9) obvi. go forth and evict those pinned VRAM objects responsibly ✨💖🎀🦋

📦 where this page comes from