STRUCT IOMMU_USER_DATA(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ NAME ✨

struct iommu_user_data β€” the iommu-driver-specific info about user space data, bestie πŸ’…

So this is the little struct that carries around what an iommu driver needs to know about a chunk of user space data. Iconic, lowkey essential.


🌸 SYNOPSIS 🌸

struct iommu_user_data {
    unsigned int type;
    void __user *uptr;
    size_t len;
 };

πŸŽ€ Members πŸŽ€

  • type β€” the data type of the user buffer. Like, what is this data, actually? πŸ‘€
  • uptr β€” pointer to the user buffer for copy_from_user. That's the address, bestie, handle with care 🫢
  • len β€” the length of the user buffer in bytes. Gotta know how much we're working with fr fr πŸ“

πŸ’– Description πŸ’–

Okay so here's the vibe: a user space data is a uAPI that's defined in include/uapi/linux/iommufd.h β€” that's the blueprint, periodt. πŸ“œ

And the rule? type, uptr and len should be just copied from an iommufd core uAPI struct. No extra seasoning, no creative liberties, just copy them straight over. Slay, but like, literally copy them. πŸ’€


πŸ¦‹ SEE ALSO πŸ¦‹


And that's the whole page, bestie! 🫢 This one lives in ./include/linux, dated October 2026, from the Kernel API Manual β€” struct iommu_user_data(9). Go off, read the source, ily. πŸ’–βœ¨

πŸ“¦ where this page comes from