iopt_pages_fill_from_xarray(9)
π iopt_pages_fill_from_xarray(9)
okay so bestie, welcome to the Kernel API Manual β this one's a lil function called iopt_pages_fill_from_xarray, and honestly? she's the fast lane. ποΈβ¨
πΈ NAME
iopt_pages_fill_from_xarray β the fast path for reading PFNs π
π SYNOPSIS
void iopt_pages_fill_from_xarray (struct iopt_pages *pages , unsigned
long start_index , unsigned long last_index , struct page **out_pages );
that's the whole vibe. returns void, so no "did it work" drama β she just does the thing. π
π¦ ARGUMENTS
pagesβ the pages we're acting on, aka the main character of this whole operation π«Άstart_indexβ the first page index in the range, like where the party starts πlast_indexβ the last page index in the range, the closing time bestie πout_pagesβ the output array where the pages get returned, the little gift bag π
β¨ DESCRIPTION
so here's the tea β β you can call this if the caller is holding a refcount on an iopt_pages_access that's known to have already been filled. when that's the case, she doesn't have to do all the slow work: she quickly reads the pages directly from the xarray. like, no cap, straight to the point. β‘
and where does this fit? it's part of the SW iommu interface to read pages for in-kernel use. iykyk π
π₯ SEE ALSO
kernel file ./drivers/iommu/iommufd/pages.c β and here's the whole friend group, all of them linked up:
iopt_area_unmap_domain(9)iopt_area_unfill_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_xarray(9)iopt_pages_rw_access(9)iopt_area_add_access(9)iopt_area_remove_access(9)
okay that's the page!! π this lil baddie lives in ./drivers/iommu/iommufd, and the version/date tag on her fit says October 2026. go read some PFNs, bestie β slay responsibly π§ββοΈπβ
π¦ 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