xe_managed_b...init_in_vram(9)

📦 version 7.3.1, in nixpkgs unstable

💅 xe_managed_bo_reinit_in_vram(9) — the kernel API manual, but make it make sense

okay bestie, so this is a page from the Kernel API Manual (yes, that one), and it's literally all about xe_managed_bo_reinit_in_vram. It's a lowercase little function, but the way it relocates your buffer objects? iconic. Let's get into it 🫶

✨ NAME ✨

xe_managed_bo_reinit_in_vram — and honestly the original NAME line just... stops there 💀 no description, no nothing. So we move.

🦋 SYNOPSIS 🦋

int xe_managed_bo_reinit_in_vram (struct xe_device *xe , struct xe_tile
*tile , struct xe_bo **src );

it returns an int, it takes three things, and it's giving "small function, big responsibilities." periodt.

🎀 ARGUMENTS 🎀

  • xe — the xe device. your main character. the whole reason we're here 💖
  • tile — the tile where the new buffer is gonna be created. that's its whole job, and it slays it.
  • src — a managed buffer object that's currently chillin' in system memory. it's about to get relocated, ngl.

🔥 DESCRIPTION 🔥

so here's the tea ☕: this function takes that managed src buffer object — the one allocated in system memory — and replaces it with a brand new one allocated in vram. and yeah, it copies the data between them, so nothing gets left behind. she's thorough. 👑

⚠️ but bestie, listen: the buffer object in VRAM is not going to have the same GGTT address. not the same. different. so the caller is fully responsible for making sure any old references to it get updated. that's on you, not on her. no cap. 😭

Returns 0 for success, or a negative error code otherwise. simple as that 💅

🧚 SEE ALSO 🧚

this list is LONG long, but I respect the hustle. every single one of these, bestie — no skipping, we don't do that here 🌸

like I said. LONG. but we ate. 🍓

💜 and that's the whole page, bestie! 💜

this lil kernel doc lives over in ./drivers/gpu/drm/xe, dated October 2026, and it's filed under xe_managed_b...init_in_vram(9) — go forth and reinit responsibly, mwah 🎀✨

📦 where this page comes from