iommu_attach_handle_get(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ iommu_attach_handle_get(9) ✨

Okay bestie, welcome to the iommu_attach_handle_get(9) page β€” this is from the Kernel API Manual, and we're about to make this whole attach-handle thing make sense. Fr fr. πŸ’–


πŸ’… NAME πŸ’…

iommu_attach_handle_get β€” Return the attach handle

🌸 SYNOPSIS 🌸

struct iommu_attach_handle * iommu_attach_handle_get (struct iommu_group
*group , ioasid_t pasid , unsigned int type );

πŸŽ€ ARGUMENTS πŸŽ€

  • group β€” the iommu group that domain was attached to
  • pasid β€” the pasid within the group
  • type β€” matched domain type, 0 for any match

πŸ¦‹ DESCRIPTION πŸ¦‹

Return handle or ERR_PTR(-ENOENT) on none, ERR_PTR(-EBUSY) on mismatch. That's the vibe check right there β€” no cap.

Return the attach handle to the caller. The life cycle of an iommu attach handle is from the time when the domain is attached to the time when the domain is detached. Callers are required to synchronize the call of iommu_attach_handle_get with domain attachment and detachment. The attach handle can only be used during its life cycle.

⚠️ Bestie, listen: the handle is only valid inside its life cycle, and you must sync the call with attach/detach. Don't be out here using it after the domain is detached β€” that's not the move. πŸ™ˆ

🌈 SEE ALSO 🌈


And that's the whole page, bestie! This one's from ./drivers/iommu, dated October 2026, and it's iommu_attach_handle_get(9) β€” go forth and sync your life cycles. πŸ’œβœ¨πŸ«Ά

πŸ“¦ where this page comes from