devm_request...e_mem_region(9)

🌸 NAME 🌸

Hey bestie, welcome to the devm_request...e_mem_region(9) page from the Kernel API Manual ✨

devm_request_free_mem_region — find free region for device private memory 💖

---

✨ SYNOPSIS ✨

okay so the signature is literally:

struct resource * devm_request_free_mem_region (struct device *dev , struct resource *base , unsigned long size );

---

🎀 ARGUMENTS 🎀

It’s giving three arguments, no cap:

• dev — device struct to bind the resource to 🫶
• base — resource tree to look in 🌈
• size — size in bytes of the device memory to add 💅

---

🦋 DESCRIPTION 🦋

So what does it do? This function tries to find an empty range of physical address big enough to contain the new resource, so that it can later be hotplugged as ZONE_DEVICE memory, which in turn allocates struct pages. That’s the whole plot, periodt 🔥

---

💜 SEE ALSO 💜

The kernel file is ./kernel/resource.c, and the resource-core guest list is:

• request_resource_conflict(9)
• request_resource(9)
• release_resource(9)
• find_next_res(9)
• walk_iomem_res_desc(9)
• region_intersects(9)
• find_resource_space(9)
• reallocate_resource(9)
• allocate_resource(9)
• lookup_resource(9)
• insert_resource_conflict(9)
• insert_resource(9)
• insert_resource_expand_to_fit(9)
• remove_resource(9)
• adjust_resource(9)
• resource_alignment(9)
• __request_region(9)
• __release_region(9)
• release_mem_region_adjustable(9)
• merge_system_ram_resource(9)
• devm_request_resource(9)
• devm_release_resource(9)
• alloc_free_mem_region(9)

---

okay that’s the page, bestie 💖 shoutout to the ./kernel source and the October 2026 date stamp, and this icon is devm_request...e_mem_region(9) — slay 🎀✨