iommu_sva_bind_device(9)

✨ NAME ✨

iommu_sva_bind_device — bind a process address space to a device 💅

Okay so welcome to a Kernel API Manual classic, bestie: we're binding a process address space to a device, and it's lowkey iconic.

🎀 SYNOPSIS 🎀

struct iommu_sva * iommu_sva_bind_device (struct device *dev , struct mm_struct *mm );

🌸 ARGUMENTS 🌸

• dev — the device. That's the whole vibe for this argument 💖
• mm — the mm to bind, and the caller must hold a reference to mm_users. Not optional, not negotiable, no cap 🫶

💖 DESCRIPTION 💖

So this function creates a bond between dev and the address space, allowing the device to access the mm using the PASID returned by iommu_sva_get_pasid. It's giving matchmaker energy for devices and address spaces 🔥

If a bond already exists between dev and mm, an additional internal reference is taken. Cute, right? But bestie, the caller must call iommu_sva_unbind_device to release each reference — every single one, periodt 💅

On error, it returns an ERR_PTR value. So yeah, keep an eye out for that 😭

🔥 SEE ALSO 🔥

• Kernel file ./drivers/iommu/iommu-sva.c
• iommu_sva_unbind_device(9)

okay bye bestie 💖 — cute sign-off from your ./drivers/iommu source/version, dated October 2026, page iommu_sva_bind_device(9) ✨🎀