iopt_area_unfill_domain(9)
πΈ iopt_area_unfill_domain(9) πΈ
okay so this is a page straight out of the Kernel API Manual bestie, and it's all about iopt_area_unfill_domain β the little cleanup gremlin that unmaps your PFNs. let's get into it π
β¨ NAME β¨
iopt_area_unfill_domain β Unmap and unpin PFNs in a domain π«Ά
π¦ SYNOPSIS π¦
void iopt_area_unfill_domain (struct iopt_area *area , struct iopt_pages
*pages , struct iommu_domain *domain );
π ARGUMENTS π
areaβ the IOVA area you're working with, bestie. that's the one.pagesβ the page supplier for the area. and yes,area->pagesisNULLhere, no cap.domainβ the domain we're unmapping from. bye girl π
π DESCRIPTION π
okay so the vibe check here: the domain should already be removed from the domains_itree before you call this. like, do that first, fr fr.
the domain itself will always get unmapped β that part is iconic and guaranteed. but the PFNs? those might not get unpinned if there are still accesses hanging around. so don't come for them until the access situation is settled, iykyk π
π SEE ALSO π
- Kernel file
./drivers/iommu/iommufd/pages.c iopt_area_unmap_domain(9)iopt_area_fill_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)
and that's the whole page, bestie π this lil beauty lives in ./drivers/iommu/iommufd, it's dated October 2026, and it goes by iopt_area_unfill_domain(9) β slay, go read the source, ily, bye πβ¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms