iommu_iotlb_...er_add_range(9)

🌸 NAME 🌸

iommu_iotlb_gather_add_range — bestie, this is the gather helper for address-based TLB invalidation. That's the whole vibe. (It's section 9, kernel API territory, so bring your compiler voice.)

---

✨ SYNOPSIS ✨

void iommu_iotlb_gather_add_range (struct iommu_iotlb_gather *gather ,
unsigned long iova , size_t size );

Yes it's one function, yes it's void, yes you're gonna pass three things. Slay. 💅

---

🎀 ARGUMENTS 🎀

• gather — the TLB gather data. This is the little bag everything gets collected into, okay? It's literally the whole point of the function. 🫶
• iova — the start of the page to invalidate. That's your where.
• size — the size of the page to invalidate. That's your how much, and ngl, "arbitrarily-sized" is the entire personality of this helper (more on that below 👀).

---

🦋 DESCRIPTION 🦋

So here's the tea, bestie: this is a helper for IOMMU drivers to build arbitrarily-sized invalidation commands — like, any size you want, the range is literally the only thing that matters here.

And the other half of the vibe? Simply minimising intermediate syncs is preferred. That's it, that's the design goal. Don't over-sync, don't be extra, just gather the range and let the syncs be minimal. Periodt. ✨

Note: it's a helper — it builds the invalidation commands for you, it doesn't do the invalidating itself, so don't come for me if you expected magic. It's giving "trust the process." 🌸

---

🔥 SEE ALSO 🔥

The kernel file in question is ./include/linux/iommu.h — that's the mothership, go say hi. 🏠

And here's the whole friend group, no cap, all of them, in order:

• struct iommu_fault_page_request(9)
• struct iommu_fault(9)
• enum iommu_page_response_code(9)
• struct iommu_page_response(9)
• struct iopf_queue(9)
• struct iommu_resv_region(9)
• struct iommu_iotlb_gather(9)
• struct iommu_dirty_bitmap(9)
• struct iommu_dirty_ops(9)
• struct iommu_user_data(9)
• struct iommu_user_data_array(9)
• __iommu_copy_struct_from_user(9)
• iommu_copy_struct_from_user(9)
• __iommu_copy_struct_from_user_array(9)
• iommu_copy_struct_from_user_array(9)
• iommu_copy_struct_from_full_user_array(9)
• __iommu_copy_struct_to_user(9)
• iommu_copy_struct_to_user(9)
• struct iommu_ops(9)
• struct iommu_domain_ops(9)
• struct iommu_device(9)
• struct iommu_fault_param(9)
• struct dev_iommu(9)
• iommu_iotlb_gather_is_disjoint(9) — the sibling that checks if your ranges are disjoint, iykyk 👀
• iommu_iotlb_gather_add_page(9) — the other sibling, single-page edition 💖
• struct iommu_fwspec(9)
• struct iommu_sva(9)
• iommu_map_sgtable(9)

---

That's the whole page, bestie — you ate that. 🍓 Go gather those ranges responsibly. 💜

Source path: ./include/linux · Version date: October 2026 · Manual: iommu_iotlb_...er_add_range(9) — mwah, see you in the next man page. 🎀🌈👑