iopt_area_split(9)

✨ iopt_area_split ✨

okay bestie, welcome to the iopt_area_split(9) page, a genuine little kernel-API moment brought to you by the manual 💅

🌸 NAME 🌸

iopt_area_split — split an area into two parts at iova 🎀

🦋 SYNOPSIS 🦋

int iopt_area_split (struct iopt_area *area , unsigned long iova );

💖 ARGUMENTS 💖

• area — the area you're about to split, bestie. this is the main character.
• iova — becomes the last of a new area ✨ like it's literally getting a whole new address and everything.

🔥 DESCRIPTION 🔥

so the way that this works is: it splits an area into two 🫶 that's it, that's the whole vibe.

it's part of the VFIO compatibility situation, and its whole reason for existing is to allow poking a hole in the mapping 💀 (yes, "poking a hole" is the actual energy here, no cap).

and here's the cute part — the two areas continue to point at the same iopt_pages, just with different starting bytes 🌈 so they're not copies, they're more like... siblings. same pages, different starting points. iconic.

⭐ SEE ALSO ⭐

kernel file ./drivers/iommu/iommufd/io_pagetable.c

• iopt_map_user_pages(9)
• iopt_map_file_pages(9)
• iopt_unmap_iova(9)
• iopt_unfill_domain(9)
• iopt_fill_domain(9)

these are the friends in the group chat, go say hi 👑

and that's the page, bestie 🍓 it lives under ./drivers/iommu/iommufd and it's dated October 2026 — mwah, sending you off with a kiss from the kernel 💜🧚