iopt_pages_fill_from_xarray(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… 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:


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