iommufd_vfi..._ioas_get_id(9)
β¨ NAME β¨
iommufd_vfio_compat_ioas_get_id β bestie, this is the one that makes sure a compat IOAS actually exists π
(this is a section 9 kernel API page from the Kernel API Manual, iykyk π)
πΈ SYNOPSIS πΈ
int iommufd_vfio_compat_ioas_get_id (struct iommufd_ctx *ictx , u32
*out_ioas_id );
okay so it hands you back an int, and yes we love a return value moment π«Ά
π¦ ARGUMENTS π¦
ictxβ the context you're operating on, like, the whole vibe you're working inside of β¨out_ioas_idβ the IOAS ID of the compatibility IOAS. this is where the answer lands, no cap π―
π DESCRIPTION π
Return the ID of the current compatibility IOAS. literally that's the whole job and it ate π₯
The ID can be passed into other functions that take an ioas_id β so think of it as the little golden ticket you hand off to your other functions so they know which IOAS you mean π
π§ SEE ALSO π§
- Kernel file
./drivers/iommu/iommufd/vfio_compat.cβ that's the main character source file right there π iommufd_vfio_compat_set_no_iommu(9)πiommufd_vfio_compat_ioas_create(9)β
not me writing a whole sign-off but fr fr this page lives in./drivers/iommu/iommufdand the version stamp says October 2026, and the page you're reading isiommufd_vfi..._ioas_get_id(9)β iconic, periodt ππ
π¦ 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