efi_load_initrd_dev_path(9)

💖 NAME 💖

okay bestie, this is the efi_load_initrd_dev_path(9) page from the Kernel API Manual ✨ The whole mood is literally: load the initrd from the Linux initrd device path. no cap 💅

🦋 SYNOPSIS 🦋

The signature is exactly this, character-for-character:

efi_status_t efi_load_initrd_dev_path (struct linux_efi_initrd *initrd ,
unsigned long max );

💅 ARGUMENTS 💅

• initrd — a pointer to the struct where we store the address the initrd was loaded at, plus the size of the loaded initrd 🎀
• max — the upper limit for the initrd memory allocation, aka the cap 🫶

✨ RETURN ✨

Here's the vibe check on the return values:

• EFI_SUCCESS — the initrd loaded successfully, and in that case load_addr and load_size are assigned accordingly 💖
• EFI_NOT_FOUND — there is no LoadFile2 protocol on the initrd device path 😭
• EFI_OUT_OF_RESOURCES — memory allocation failed 💀
• EFI_LOAD_ERROR — in all other cases 🙈

🎀 SEE ALSO 🎀

• Kernel file ./drivers/firmware/efi/libstub/efi-stub-helper.c
• efi_parse_options(9)
• efi_exit_boot_services(9)
• get_efi_config_table(9)
• efi_load_initrd(9)
• efi_wait_for_key(9)
• efi_remap_image(9)

mwah 💋 this cutie comes from source ./drivers/firmware/efi/libstub and is dated October 2026. slay, periodt 🌈