xe_bo_can_migrate(9)

📦 version 7.3.1, in nixpkgs unstable

💖 xe_bo_can_migrate(9) — Kernel API Manual 💖

okay so bestie, this is the whole vibe for xe_bo_can_migrate(9) from the Kernel API Manual — yes, the manual name is folded right up here like a little bow 🎀. It’s giving “can this buffer object migrate?” energy, and I’m obsessed.

✨ NAME ✨

xe_bo_can_migrate — whether a buffer object likely can be migrated 💫

🎀 SYNOPSIS 🎀

bool xe_bo_can_migrate (struct xe_bo *bo , u32 mem_type );

🫶 ARGUMENTS 🫶

  • bo — the buffer object to migrate, aka the main character here 👑
  • mem_type — the TTM memory type intended to migrate to, so like the destination vibe check 🌈

💅 DESCRIPTION 💅

okay so what this does is check whether the buffer object supports migration to the given memory type. no cap, that’s the whole point.

⚠️ important: pinning may affect the ability to migrate as returned by this function — so the answer can lowkey change if somebody’s got it pinned, bestie.

this function is primarily intended as a helper for checking the possibility to migrate buffer objects, and it can be called without the object lock held. slay, no lock required, periodt.

🔥 RETURN 🔥

true if migration is possible, false otherwise. that’s it, that’s the tea ☕✨

🌸 SEE ALSO 🌸

the kernel file is ./drivers/gpu/drm/xe/xe_bo.c, and the whole squad is right here — every single one, no skips:

and that’s the page, bestie 🫶 this cutie came from ./drivers/gpu/drm/xe, dated October 2026, and it’s literally titled xe_bo_can_migrate(9) — bye, love u, stay slay 💅💖

📦 where this page comes from