xe_tile_init_noalloc(9)

💅 xe_tile_init_noalloc 💅

okay so bestie, welcome to the Kernel API Manual ✨ — yes it's a 9 section page, yes it's a kernel function, no you don't have to be scared. this one is literally xe_tile_init_noalloc, and it's giving "get the tile ready without touching the snacks" vibes 🎀

---

🌸 NAME 🌸

xe_tile_init_noalloc — init the tile up to the point where allocations can happen. that's it, that's the whole job 🫶

---

✨ SYNOPSIS ✨

int xe_tile_init_noalloc (struct xe_tile *tile );

---

🦋 ARGUMENTS 🦋

• tile — the tile you're initializing, bestie. the actual struct xe_tile * you're handing over. that's the one.

---

💖 DESCRIPTION 💖

okay so here's the tea ☕ — this function gets the tile ready so that memory allocations to VRAM can happen later, but it is not allowed to allocate memory itself. like, it's setting up the vibe, not buying the drinks. 🧚

this state is highkey useful for display readout, and here's why: the inherited display framebuffer would otherwise get overwritten, because it's usually put at the start of VRAM. 😭 so yeah, this function exists to not stomp on that. iconic behavior honestly 👑

note that since this is tile initialization, it should not perform any GT-specific operations, and thus does not need to hold GT forcewake. no cap, that's just how it is 💅

---

⭐ RETURN ⭐

• 0 on success 🎉
• a negative error code on error 💀

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/gpu/drm/xe/xe_tile.c
• Multi-tile Design(9)
• xe_tile_alloc(9)
• xe_tile_alloc_vram(9)
• xe_tile_init_early(9)
• xe_tile_local_pagemap(9)

like, go read those too, iykyk 🍓

---

and that's the whole page, bestie — brought to you by ./drivers/gpu/drm/xe, dated October 2026, and yes it's still xe_tile_init_noalloc(9) but now it's cute 💜 mwah! 🎀