xe_ggtt_init_early(9)

💅 xe_ggtt_init_early (9) — from the Kernel API Manual, bestie 🎀

okay so like, the manual name is literally right there in the title: Kernel API Manual, section 9. we're in the kernel docs now, put your hair up, we're getting technical. ✨

---

🌸 NAME 🌸

xe_ggtt_init_early — Early GGTT initialization, no cap 💖

---

✨ SYNOPSIS ✨

int xe_ggtt_init_early (struct xe_ggtt *ggtt );

that's it. one function, one argument, it's giving "small but mighty" 🦋

---

🎀 ARGUMENTS 🎀

• ggtt — the struct xe_ggtt that's about to get initialized. that's the one, that's the whole argument, icl it's very low-maintenance 💅

---

💜 DESCRIPTION 💜

okay so the whole vibe here is: this lets you create new mappings usable by the GuC. GuC bestie gets access, she's thriving, she's slay. 👑

but — and this is the part you cannot skip — those mappings are not usable by the HW engines. nope. not yet. not today. because it doesn't have scratch and there's no initial clear done to it yet. 😭 that's the whole thing, that's the situation.

that stuff — the scratch, the initial clear — happens later, in the regular, non-early GGTT initialization. so like, this is the trailer, not the movie. the appetizer, not the entrée. the early one. iykyk 🧚

---

⭐ RETURN ⭐

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

that's it. classic kernel binary. no notes. 🫶

---

🦋 SEE ALSO 🦋

the whole friend group, gathered in one place, fr fr:

• Kernel file ./drivers/gpu/drm/xe/xe_ggtt.c
• Global Graphics Translation Table (GGTT)(9)
• struct xe_ggtt_node(9)
• struct xe_ggtt_pt_ops(9)
• struct xe_ggtt(9)
• xe_ggtt_start(9)
• xe_ggtt_size(9)
• xe_ggtt_alloc(9)
• xe_ggtt_node_remove(9)
• xe_ggtt_init(9)
• xe_ggtt_shift_nodes(9)
• xe_ggtt_insert_node(9)
• xe_ggtt_node_pt_size(9)
• xe_ggtt_map_bo(9)
• xe_ggtt_map_bo_unlocked(9)
• xe_ggtt_insert_node_transform(9)
• xe_ggtt_insert_bo_at(9)
• xe_ggtt_insert_bo(9)
• xe_ggtt_remove_bo(9)
• xe_ggtt_largest_hole(9)
• xe_ggtt_assign(9)
• xe_ggtt_node_save(9)
• xe_ggtt_node_load(9)
• xe_ggtt_dump(9)
• xe_ggtt_print_holes(9)
• xe_ggtt_encode_pte_flags(9)
• xe_ggtt_read_pte(9)
• xe_ggtt_node_addr(9)
• xe_ggtt_node_size(9)

like i said. the whole group chat. 🌈

---

ok real talk — this one's an early init. if you're expecting the HW engines to be able to touch those mappings, they can't, not yet. no scratch, no initial clear. read the DESCRIPTION again bestie, i'm serious 🙈

---

and that's a wrap!! 🍓 this came out of ./drivers/gpu/drm/xe, dated October 2026, and it's the xe_ggtt_init_early(9) page from the Kernel API Manual — bye, love u, go read xe_ggtt_init(9) next 💖💅