efi_allocate_pages_aligned(9)

💖 NAME 💖

efi_allocate_pages_aligned — Allocate memory pages ✨

okay bestie, this is the Kernel API Manual page for efi_allocate_pages_aligned(9), and it’s giving “let’s grab some aligned memory pages” energy, fr fr 🫶

✨ SYNOPSIS ✨

efi_status_t efi_allocate_pages_aligned (unsigned long size , unsigned
long *addr , unsigned long max , unsigned long align , int memory_type
);

🎀 ARGUMENTS 🎀

• size — the minimum number of bytes to allocate, bestie. Like the smallest bag you’re willing to carry 💅
• addr — on return, this is the address of the first allocated page. And listen: that first allocated page has alignment EFI_ALLOC_ALIGN, which is an architecture dependent multiple of the page size 👑
• max — the address that the last allocated memory page shall not exceed. So it’s the “do not pass go” boundary, no cap 🚧
• align — the minimum alignment of the base of the allocation. Alignment queen behavior ✨
• memory_type — the type of memory to allocate. Gotta know the vibe of the memory you’re requesting 🧚

🦋 DESCRIPTION 🦋

So this function allocates pages as EFI_LOADER_DATA 🌈. The allocated pages are aligned according to align, which should be >= EFI_ALLOC_ALIGN — that’s the rule, bestie, don’t skip it. The last allocated page will not exceed the address given by max 🙅‍♀️. That’s literally the whole plot: allocate pages, keep them aligned, and stay under max.

💅 RETURN 💅

The return value is a status code 😌. That’s your vibe check after the call — it tells you how things went, periodt.

👑 SEE ALSO 👑

Kernel file ./drivers/firmware/efi/libstub/alignedmem.c — go peek if you’re obsessed like me 💖

and that’s the page, bestie! source/version: ./drivers/firmware/efi/libstub, date: October 2026, and yeah it’s the efi_allocate_pages_aligned(9) page 🫶✨