for_each_reserved_mem_range(9)

📦 version 7.3.1, in nixpkgs unstable

💅 for_each_reserved_mem_range(9) — Kernel API Manual 🎀

okay bestie, so we're in the Kernel API Manual today and the star of the show is for_each_reserved_mem_range — yes it's a long name, yes it ate, let's get into it ✨

🌸 NAME 🌸

for_each_reserved_mem_range — iterate over all reserved memblock areas 💖

Literally what it says on the tin. It loops over the reserved bits. Slay.

✨ SYNOPSIS ✨

for_each_reserved_mem_range (i , p_start , p_end );

That's the whole vibe. Three args, no cap. 🫶

🦋 ARGUMENTS 🦋

  • i — a u64 used as the loop variable. it's your counter bestie, it just keeps going 🎢
  • p_start — ptr to phys_addr_t for the start address of the range, can be NULL. so like, it points at where the range begins — and if you don't care to know, NULL is totally valid, king behavior 👑
  • p_end — ptr to phys_addr_t for the end address of the range, can be NULL. same deal, it's the end of the range, and again NULL is allowed if you're not nosy 🙈

🌈 DESCRIPTION 🌈

Walks over reserved areas of memblock. Available as soon as memblock is initialized.

That's it. That's the whole thing. It's giving "small but mighty" energy — you don't need memblock to be fully grown up or anything, the second it's initialized this bad boy is ready to go 🔥

no cap, this is genuinely one of the short ones. enjoy it while it lasts bestie, some of the neighbors in SEE ALSO are long 😭

🔥 SEE ALSO 🔥

okay so this is the friend group 🫶 — the kernel file lives at ./include/linux/memblock.h, and here's everyone else:

the whole for_each_* cinematic universe fr fr 👑💜

and that's the page diva 💅 — sourced from ./include/linux, dated October 2026, and yes it's still called for_each_reserved_mem_range(9) because we don't do rebrands here 🎀✨

📦 where this page comes from