firmware_map_find_entry(9)

💖 firmware_map_find_entry(9) 💖

okay so bestie, welcome to the Kernel API Manual — this one's a little lookup page for the firmware memory map, and it's honestly giving "librarian with a clipboard" energy 🎀

---

✨ NAME ✨

firmware_map_find_entry — search for a memmap entry inside map_entries. that's it, that's the whole job 💅

---

🌸 SYNOPSIS 🌸

struct firmware_map_entry * firmware_map_find_entry (u64 start , u64 end , const char *type );

---

🦋 ARGUMENTS 🦋

• start — start of the memory range 🫶
• end — end of the memory range, and heads up, it's exclusive (so the end itself is not included, she's a boundary not a member 💀)
• type — the type of the memory range ✨

---

💜 DESCRIPTION 💜

so this function's whole thing is finding the memmap entry for a given memory range. no cap, that's it. 🧚

⚠️ but listen — the caller must hold map_entries_lock, and must not release that lock until the processing of the returned entry has completed. like, do not let go of that lock early, that's the rule, periodt. 🔥

---

⭐ RETURN ⭐

pointer to the entry that was found on success 🎉 … or NULL on failure 😭

---

🌈 SEE ALSO 🌈

kernel file ./drivers/firmware/memmap.c plus the whole squad: firmware_map_add_entry(9), firmware_map_remove_entry(9), firmware_map_find_entry_in_list(9), firmware_map_find_entry_bootmem(9), firmware_map_add_hotplug(9), firmware_map_add_early(9), firmware_map_remove(9) 👑

---

and that's the page!! 🍓 sourced from that ./drivers/firmware life, stamped October 2026 — go find your entries bestie, ily 💖🦋