ENUM IOMMUFD_OPTION_OPS(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… enum iommufd_option_ops(9) β€” from the Kernel API Manual, bestie

okay so we're in the Kernel API Manual and today's main character is enum iommufd_option_ops, which is lowkey just the two vibes you can pass to ioctl(IOMMU_OPTION_OP_SET) and ioctl(IOMMU_OPTION_OP_GET). That's it. That's the whole personality. And honestly? Iconic for it.


✨ NAME ✨

enum iommufd_option_ops β€” the enum behind ioctl(IOMMU_OPTION_OP_SET) and ioctl(IOMMU_OPTION_OP_GET) πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

enum iommufd_option_ops {
    IOMMU_OPTION_OP_SET ,
    IOMMU_OPTION_OP_GET

};

🌸 Constants 🌸

Two constants, two moods, no notes:

  • IOMMU_OPTION_OP_SET β€” bestie, this one sets the option's value. you're the one writing here πŸ’…
  • IOMMU_OPTION_OP_GET β€” and this one gets the option's value. no thoughts, just reading, and honestly relatable πŸ™ˆ
ngl there's genuinely nothing else in this enum β€” it's a two-item situation and we respect it.

πŸ‘‘ SEE ALSO πŸ‘‘

the whole extended friend group, fr fr β€” starting with the source file itself, ./include/uapi/linux/iommufd.h, plus the general ioctl format(9), and then deep breath:

  • struct iommu_destroy(9)
  • struct iommu_ioas_alloc(9)
  • struct iommu_iova_range(9)
  • struct iommu_ioas_iova_ranges(9)
  • struct iommu_ioas_allow_iovas(9)
  • enum iommufd_ioas_map_flags(9)
  • struct iommu_ioas_map(9)
  • struct iommu_ioas_noiommu_get_pa(9)
  • struct iommu_ioas_map_file(9)
  • struct iommu_ioas_copy(9)
  • struct iommu_ioas_unmap(9)
  • enum iommufd_option(9)
  • struct iommu_option(9)
  • enum iommufd_vfio_ioas_op(9)
  • struct iommu_vfio_ioas(9)
  • enum iommufd_hwpt_alloc_flags(9)
  • enum iommu_hwpt_vtd_s1_flags(9)
  • struct iommu_hwpt_vtd_s1(9)
  • struct iommu_hwpt_arm_smmuv3(9)
  • struct iommu_hwpt_amd_guest(9)
  • enum iommu_hwpt_data_type(9)
  • struct iommu_hwpt_alloc(9)
  • enum iommu_hw_info_vtd_flags(9)
  • struct iommu_hw_info_vtd(9)
  • enum iommu_hw_info_arm_smmuv3_flags(9)
  • struct iommu_hw_info_arm_smmuv3(9)
  • struct iommu_hw_info_tegra241_cmdqv(9)
  • struct iommu_hw_info_amd(9)
  • enum iommu_hw_info_type(9)
  • enum iommufd_hw_capabilities(9)
  • enum iommufd_hw_info_flags(9)
  • struct iommu_hw_info(9)
  • struct iommu_hwpt_set_dirty_tracking(9)
  • enum iommufd_hwpt_get_dirty_bitmap_flags(9)
  • struct iommu_hwpt_get_dirty_bitmap(9)
  • enum iommu_hwpt_invalidate_data_type(9)
  • enum iommu_hwpt_vtd_s1_invalidate_flags(9)
  • struct iommu_hwpt_vtd_s1_invalidate(9)
  • struct iommu_viommu_arm_smmuv3_invalidate(9)
  • struct iommu_hwpt_invalidate(9)
  • enum iommu_hwpt_pgfault_flags(9)
  • enum iommu_hwpt_pgfault_perm(9)
  • struct iommu_hwpt_pgfault(9)
  • enum iommufd_page_response_code(9)
  • struct iommu_hwpt_page_response(9)
  • struct iommu_fault_alloc(9)
  • enum iommu_viommu_type(9)
  • struct iommu_viommu_tegra241_cmdqv(9)
  • struct iommu_viommu_alloc(9)
  • struct iommu_vdevice_alloc(9)
  • struct iommu_ioas_change_process(9)
  • enum iommu_veventq_flag(9)
  • struct iommufd_vevent_header(9)
  • enum iommu_veventq_type(9)
  • struct iommu_vevent_arm_smmuv3(9)
  • struct iommu_vevent_tegra241_cmdqv(9)
  • struct iommu_veventq_alloc(9)
  • enum iommu_hw_queue_type(9)
  • struct iommu_hw_queue_alloc(9)

like I said. entire friend group. every single one of them pulled up to the function πŸ’€πŸ«Ά


that's the whole page bestie!! sourced from ./include/uapi/linux, dated October 2026 β€” mwah, go set (or get) an option, slay πŸ’–βœ¨πŸ§š

πŸ“¦ where this page comes from