efi_get_memory_map(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 efi_get_memory_map(9) 🌸

okay so bestie, welcome to the Kernel API Manual β€” yes, THE kernel API manual, we're doing big things today πŸ’… this one's all about grabbing yourself a memory map, and it's honestly kind of iconic.


✨ NAME ✨

efi_get_memory_map β€” get memory map πŸ—ΊοΈ (that's it, that's the whole vibe)


πŸŽ€ SYNOPSIS πŸŽ€

efi_status_t efi_get_memory_map (struct efi_boot_memmap **map , bool
install_cfg_tbl );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • map β€” a pointer to a memory map pointer, and that's where the newly allocated memory map gets assigned fr fr. it's pointer-to-a-pointer, she's layered, she's complex, we love her 🫢
  • install_cfg_tbl β€” a bool that decides whether or not you're installing the boot memory map as a configuration table. yes or no, bestie, no in-between πŸ™ˆ

πŸ’– DESCRIPTION πŸ’–

so what does she actually DO? literally just retrieves the UEFI memory map. that's the whole personality πŸ’€

but here's the detail you can't skip: the allocated memory leaves room for up to EFI_MMAP_NR_SLACK_SLOTS additional memory map entries β€” so there's built-in wiggle room, she's extra in the best way, main character energy honestly ✨


⭐ RETURN ⭐

status code. that's the answer, she returns a status code 😌


🌈 SEE ALSO 🌈

go read those too, iykyk πŸ“š


kay that's the whole page bestie, you ate that πŸ’… this lil gem lives in ./drivers/firmware/efi/libstub, dated October 2026, and it's efi_get_memory_map(9) β€” go forth and map some memory, mwah πŸ“πŸ§š

πŸ“¦ where this page comes from