efi_memmap_split_count(9)

💅 efi_memmap_split_count(9)

okay so bestie, welcome to the glow-up of efi_memmap_split_count — it lives in the Kernel API Manual and honestly? it's a tiny little icon and it knows it ✨

---

🌸 NAME 🌸

efi_memmap_split_count — literally just counts how many additional EFI memmap entries you're gonna need 🎀

---

🦋 SYNOPSIS 🦋

int efi_memmap_split_count (efi_memory_desc_t *md , struct range *range );

that's it, that's the whole vibe check: it takes two things and hands you back an int 💖

---

💅 ARGUMENTS 💅

• md — the EFI memory descriptor you're about to split, no cap 🫶
• range — the address range (start, end) that you want to split around, iykyk 🌈

---

✨ DESCRIPTION ✨

so the way that this works: it returns the number of additional EFI memmap entries required to accommodate range 🔥

that's the whole function, bestie — it counts, it doesn't do the splitting, it's giving "I'm the planner, not the doer" main character energy 👑

---

👑 SEE ALSO 👑

• Kernel file ./arch/x86/platform/efi/memmap.c 🍓
• efi_memmap_alloc(9) — the allocator bestie 🧚
• efi_memmap_install(9) — the installer bestie 💜
• efi_memmap_insert(9) — the inserter bestie ⭐

---

and that's a wrap!! 🎀 this little cutie comes to you from ./arch/x86/platform/efi, dated October 2026 — screenshot it, frame it, obsess over it 💖✨🌸🦋💅