memblock_re...ved_base_pfn(9)

✨ memblock_region_reserved_base_pfn — Kernel API Manual ✨

okay bestie so this is a page from the Kernel API Manual, and the function is memblock_region_reserved_base_pfn 💖 (yes the title got squished to memblock_re...ved_base_pfn in the header, that's just the terminal being dramatic, she's fine).

🌸 NAME 🌸

memblock_region_reserved_base_pfn — get the lowest pfn of the reserved region 🎀

🦋 SYNOPSIS 🦋

unsigned long memblock_region_reserved_base_pfn (const struct memblock_region *reg );

💅 ARGUMENTS 💅

• reg — the memblock_region structure, iykyk 👑

⭐ RETURN ⭐

the lowest pfn intersecting with the reserved region 🫶

🌈 SEE ALSO 🌈

Kernel file ./include/linux/memblock.h — and literally the whole friend group shows up here, no cap:

• enum memblock_flags(9)
• struct memblock_region(9)
• struct memblock_type(9)
• struct memblock(9)
• for_each_physmem_range(9)
• __for_each_mem_range(9)
• __for_each_mem_range_rev(9)
• for_each_mem_range(9)
• for_each_mem_range_rev(9)
• for_each_reserved_mem_range(9)
• for_each_mem_pfn_range(9)
• for_each_free_mem_range(9)
• for_each_free_mem_range_reverse(9)
• memblock_set_current_limit(9)
• memblock_region_memory_base_pfn(9)
• memblock_region_memory_end_pfn(9)
• memblock_region_reserved_end_pfn(9)
• for_each_mem_region(9)
• for_each_reserved_mem_region(9)

lowkey a whole squad of for_each_* macros just to say hi 😭 but that's the memblock life bestie, we stan a thorough cross-reference list 💀✨

and that's the whole page, mwah 💋 — this one's living in ./include/linux, dated October 2026, and it's signed off as memblock_re...ved_base_pfn(9) because the header and footer both refuse to spell the whole thing out 🙈 every single time, fr fr. bye bestie, go read a for_each_reserved_mem_region(9) for me 🎀🦋💜