iopt_pages_rw_access(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… iopt_pages_rw_access(9) β€” Kernel API Manual πŸŽ€

okay so bestie, this is iopt_pages_rw_access(9) from the Kernel API Manual, and it's literally giving β€œcopy to/from a linear slice of the pages” energy. let's get into it ✨

🌸 NAME 🌸

iopt_pages_rw_access β€” Copy to/from a linear slice of the pages

✨ SYNOPSIS ✨

int iopt_pages_rw_access (struct iopt_pages *pages , unsigned long
start_byte , void *data , unsigned long length , unsigned int flags );

πŸŽ€ ARGUMENTS πŸŽ€

  • pages β€” pages to act on. the main characters, fr 🫢
  • start_byte β€” First byte of pages to copy to/from. like where the slay begins ✨
  • data β€” Kernel buffer to get/put the data. the little vessel for your bytes πŸŽ€
  • length β€” Number of bytes to copy. exactly how much we're moving, no cap πŸ’…
  • flags β€” IOMMUFD_ACCESS_RW_* flags. the flag set, iykyk πŸ‘‘

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so here's the vibe: this will find each page in the range, kmap it and then memcpy to/from the given kernel buffer. that's the whole little routine, and it ate. πŸ’…

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./drivers/iommu/iommufd/pages.c β€” go read it, bestie 🫢


mwah πŸ’– source/version ./drivers/iommu/iommufd, date October 2026, page iopt_pages_rw_access(9) β€” periodt. 🫢

πŸ“¦ where this page comes from