iommufd_device_bind(9)

iommufd_device_bind(9) 💖

okay so welcome to the Kernel API Manual page for iommufd_device_bind(9) — the routine that binds a physical device to an iommu fd. bestie, this is your ownership handshake, and it's lowkey important 🫶

✨ NAME ✨

iommufd_device_bind — bind a physical device to an iommu fd. that's the whole vibe 💅

🦋 SYNOPSIS 🦋

       struct iommufd_device * iommufd_device_bind (struct iommufd_ctx *ictx ,
       struct device *dev , u32 *id );

💅 ARGUMENTS 💅

• ictx — the iommufd file descriptor. yes, the fd in question.
• dev — pointer to a physical device struct. the actual device bestie.
• id — output ID number to return to userspace for this device. it's giving "here's your ID, userspace" 🎀

🌸 DESCRIPTION 🌸

when the bind succeeds, it establishes ownership over the device and gives you back a struct iommufd_device pointer. if it doesn't succeed? you get an error pointer instead. no in-between 😭

🚨 important: a driver using this API must set driver_managed_dma and must not touch the device until this routine succeeds and establishes ownership. like, do not poke the device before ownership is actually yours, periodt 💀

binding a PCI device places the entire RID under iommufd control. the whole RID. not a slice, not a snack — the entire thing 👑

and listen: the caller must undo this with iommufd_device_unbind. no leaving it bound and ghosting it, bestie 💅

🔥 SEE ALSO 🔥

the kernel file is ./drivers/iommu/iommufd/device.c — go peek if you're nosy 👀

• iommufd_ctx_has_group(9)
• iommufd_device_unbind(9)
• iommufd_device_attach(9)
• iommufd_device_replace(9)
• iommufd_device_detach(9)
• iommufd_access_create(9)
• iommufd_access_destroy(9)
• iommufd_access_notify_unmap(9)
• iommufd_access_unpin_pages(9)
• iommufd_access_pin_pages(9)
• iommufd_access_rw(9)

xoxo, your kernel bestie 💅 — source/version: ./drivers/iommu/iommufd · date: October 2026 · page: iommufd_device_bind(9) ✨