iort_iommu_get_resv_regions(9)

💖 NAME 💖

iort_iommu_get_resv_regions — bestie, it's the generic helper for grabbing reserved regions ✨

okay so real quick before anything else: this little icon lives in the Kernel API Manual (section 9, kernel developer land 🫶), and it's genuinely just a friendly middleman that goes and fetches the reserved regions for you. no cap.

---

🦋 SYNOPSIS 🦋

void iort_iommu_get_resv_regions (struct device *dev , struct list_head *head );

look at her. void, two pointers, zero drama. she takes exactly what you give her and returns nothing because the list is the whole point, iykyk 💅

---

🎀 ARGUMENTS 🎀

• dev — the device, straight from iommu_get_resv_regions. that's your main character right there 👑
• head — the reserved region list, also straight from iommu_get_resv_regions. this is where the regions end up, so like… don't lose her 🙈

both args come from the same place, they're literally a matching set, and yes that's iconic of them 💜

---

🌈 SEE ALSO 🌈

the kernel file she lives in is ./drivers/acpi/arm64/iort.c — go say hi to the whole squad while you're there, they're all serving:

• iort_set_fwnode(9)
• iort_get_fwnode(9)
• iort_delete_fwnode(9)
• iort_get_iort_node(9)
• iort_register_domain_token(9)
• iort_deregister_domain_token(9)
• iort_find_domain_token(9)
• iort_msi_map_id(9)
• iort_msi_xlate(9)
• iort_pmsi_get_msi_info(9)
• iort_dev_find_its_id(9)
• iort_get_device_domain(9)
• iort_get_platform_device_domain(9)
• iort_get_rmr_sids(9)
• iort_put_rmr_sids(9)
• iort_iommu_configure_id(9)
• iort_dma_get_ranges(9)
• iort_add_platform_device(9)

like, that's a whole friend group and they ALL have manual pages. obsessed honestly 🍓

---

and that's the whole page bestie, she's short and sweet and does exactly one job 💀✨

---

kisses, this has been ./drivers/acpi/arm64, dated October 2026, signing off as iort_iommu_get_resv_regions(9) 🧚💖 periodt.