iommu_replace_group_handle(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay so bestie, you're looking at the Kernel API Manual page for iommu_replace_group_handle(9) πŸ’–βœ¨ and it's genuinely such a useful lil domain-switcher.

πŸŽ€ NAME πŸŽ€

iommu_replace_group_handle β€” replace the domain that a group is attached to. That's the whole vibe, no cap πŸ’…


✨ SYNOPSIS ✨

int iommu_replace_group_handle (struct iommu_group *group , struct
       iommu_domain *new_domain , struct iommu_attach_handle *handle );

🫢 ARGUMENTS 🫢

  • group β€” the IOMMU group that will be attached to the new domain. She's the main character getting moved πŸ’«
  • new_domain β€” the new IOMMU domain to replace with. Fresh domain, who dis? πŸ¦‹
  • handle β€” attach handle. The little connector bestie we're handing over πŸŽ€

🌸 DESCRIPTION 🌸

This API lets the group switch domains without being forced to go to the blocking domain in-between. Lowkey efficient, highkey iconic. It also lets the caller provide an attach handle for the new domain and use it when the domain is attached ✨

If the currently attached domain is a core domain (e.g. a default_domain), it will act just like iommu_attach_group_handle. Same behavior, different day, periodt πŸ’…

⚠️ Caller should always provide a new handle to avoid a race with the paths that have a lockless reference to handle. Like, do not skip this, bestie β€” it's giving important 🚨

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file: ./drivers/iommu/iommu.c


xoxo, this cutie page comes from ./drivers/iommu, version/date October 2026 πŸŽ€πŸ’– slay and goodbye bestie ✨

πŸ“¦ where this page comes from