efi_memmap_alloc(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ efi_memmap_alloc(9) ✨

okay so bestie, welcome to the Kernel API Manual πŸ’… this one's all about efi_memmap_alloc β€” the little function that gets your EFI memory map its very own memory. iconic behavior, honestly.


🌸 NAME 🌸

efi_memmap_alloc β€” Allocate memory for the EFI memory map

like literally, it's the allocator for the EFI memory map. that's the whole vibe. 🫢


πŸŽ€ SYNOPSIS πŸŽ€

int efi_memmap_alloc (unsigned int num_entries , struct efi_memory_map_data *data );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • num_entries β€” Number of entries in the allocated map. yes bestie, it's literally how many entries your allocated map is gonna have. count 'em. πŸ”₯
  • data β€” efi memmap installation parameters. the whole setup-info situation for installing that memmap. πŸ’–

πŸ‘‘ DESCRIPTION πŸ‘‘

Depending on whether mm_init has already been invoked or not, either memblock or "normal" page allocation is used. so yeah β€” the function checks if mm_init has run yet, and picks its allocation strategy accordingly. lowkey adaptive. 🧚

Returns zero on success, a negative error code on failure. no cap: 0 means slay, negative means something went wrong. 😭


🌈 SEE ALSO 🌈

Kernel file ./arch/x86/platform/efi/memmap.c, plus the whole friend group: efi_memmap_install(9), efi_memmap_split_count(9), efi_memmap_insert(9). go read them, iykyk πŸ’œ


and that's the page, bestie! brought to you by the ./arch/x86/platform/efi source, version vibes, dated October 2026 β€” periodt. πŸŽ€βœ¨πŸ’…

πŸ“¦ where this page comes from