iopt_area_fill_domain(9)

🎀 iopt_area_fill_domain(9) 🎀

okay so bestie, this is <pink>iopt_area_fill_domain(9)</pink> from the Kernel API Manual, and it's literally giving “Map PFNs from the area into a domain” main-character energy ✨. Let's get into it, no cap.

✨ NAME ✨

iopt_area_fill_domain — Map PFNs from the area into a domain 💖

🫶 SYNOPSIS 🫶

int iopt_area_fill_domain (struct iopt_area *area , struct iommu_domain *domain );

💅 ARGUMENTS 💅

• area — the IOVA area to use. That's your turf, your vibe, your area 🦋
• domain — the domain to load PFNs into. This is where the PFNs are headed, periodt 💫

🔥 DESCRIPTION 🔥

okay so here's the tea: it reads the pfns from the area's underlying iopt_pages and maps them into the given domain. Lowkey iconic behavior, honestly 🫶.

It's called when attaching a new domain to an io_pagetable — like when a new domain slides into the io_pagetable group chat 🌸✨.

🌈 SEE ALSO 🌈

• Kernel file ./drivers/iommu/iommufd/pages.c 👀
• iopt_area_unmap_domain(9)
• iopt_area_unfill_domain(9)
• iopt_area_fill_domains(9)
• iopt_area_unfill_domains(9)
• iopt_pages_unfill_xarray(9)
• iopt_pages_fill_from_xarray(9)
• iopt_pages_fill_xarray(9)
• iopt_pages_rw_access(9)
• iopt_area_add_access(9)
• iopt_area_remove_access(9)

mwah 💋 — source/version is ./drivers/iommu/iommufd, dated October 2026, and this whole page is iopt_area_fill_domain(9). bye bestie 🎀✨