iommufd_vfi..._ioas_create(9)

✨ iommufd_vfi..._ioas_create(9) ✨

okay so this is a page from the Kernel API Manual, and bestie, it's a short one but it's lowkey important — welcome to the group chat 🫶

---

💖 NAME 💖

iommufd_vfio_compat_ioas_create — bestie, this one's whole job is making sure the compat IOAS actually gets created ✨

---

🎀 SYNOPSIS 🎀

int iommufd_vfio_compat_ioas_create (struct iommufd_ctx *ictx );

like, that's literally the whole signature. she's compact 👑

---

🦋 ARGUMENTS 🦋

• ictx — the context you're operating on. that's it, that's the argument, she's not complicated 💅

---

🌸 DESCRIPTION 🌸

okay so picture this: the compatibility IOAS is the IOAS that the vfio compatibility ioctls operate on — and the reason they need a special one is that those ioctls just don't have an IOAS ID input in their ABI. like, the slot for it isn't even there in the struct. so instead of you telling it which IOAS, it just... has to have one ready for you 🙈

now here's the vibe check: only attaching a group should cause a default creation of the internal ioas. that's the trigger, that's the main character moment, nothing else does it ✨

and this function? it does nothing if an existing ioas has already been assigned somehow — like, she checks, sees one's already there, and goes "k slay, ur already sorted 💅" and leaves it alone. no duplicating, no overwriting, no drama. periodt.

---

💜 SEE ALSO 💜

• Kernel file ./drivers/iommu/iommufd/vfio_compat.c — go read the source bestie, it's right there 📂
• iommufd_vfio_compat_ioas_get_id(9) — the one that hands you the ID 🆔
• iommufd_vfio_compat_set_no_iommu(9) — the one for when there's no iommu in the picture 🚫

---

and that's the whole page!! short and sweet, just the way we like it 🍓

this came from ./drivers/iommu/iommufd and it's dated October 2026 — so mark your calendars, note the source, and stan a tidy little kernel function that knows when to do nothing 💖✨🎀🦋