vmemmap_remap_alloc(9)

💅 vmemmap_remap_alloc(9) 💅

okay so bestie, welcome to the Kernel API Manual — yes we're reading kernel docs together, this is our bonding era 🫶. This page is all about vmemmap_remap_alloc, and ngl it's a whole vibe once you get past the intimidating name.

---

✨ NAME ✨

vmemmap_remap_alloc — remaps the vmemmap virtual address range [@start, end) so it points at the page that comes from the @vmemmap_pages respectively. like, it's doing a little address-range glow-up 💫

---

🌸 SYNOPSIS 🌸

int vmemmap_remap_alloc (unsigned long start , unsigned long end ,
       unsigned long flags );

three unsigned longs walk into a function and return an int, no cap 😌

---

🎀 ARGUMENTS 🎀

• start — the start address of the vmemmap virtual address range we're remapping. the beginning of the glow-up zone, literally 🦋
• end — the end address of that same vmemmap virtual address range we're remapping. the range is [start, end), so end is the boundary, not included — periodt ✨
• flags — the modifications to the vmemmap_remap_walk flags. this is where you tell it how you want the walk to behave 🎯

---

🔥 RETURN 🔥

• 0 on success — slay, we ate 💅
• a negative error code otherwise — it's giving "nope, not today" 😭

---

👑 SEE ALSO 👑

• Kernel file ./mm/hugetlb_vmemmap.c — the source file where the magic lives, iykyk 🧚
• struct vmemmap_remap_walk(9)
• vmemmap_remap_split(9)
• vmemmap_remap_free(9)
• hugetlb_vmemmap_restore_folio(9)
• hugetlb_vmemmap_restore_folios(9)
• hugetlb_vmemmap_optimize_folio(9)

all of these are the friend group of this function — go say hi 💖

---

lowkey reminder: start and end are a half-open range, [start, end), so don't be out here expecting end to be included, bestie 🙈

---

and that's the page!! 🎀 this one lives in ./mm, dated October 2026, and it's filed under vmemmap_remap_alloc(9) — mwah, go forth and remap responsibly 🌈⭐💜