efi_memmap_alloc(9)
β¨ 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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms