ENUM IOMMU_HW_INFO_ARM_SMMUV3_FLAGS(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… enum iommu_hw_info_arm_smmuv3_flags β€” NAME

okay so bestie, welcome to the Kernel API Manual ✨ this lil page is all about enum iommu_hw_info_arm_smmuv3_flags β€” which is literally just the flags for ARM SMMUv3 hw_info. that's it, that's the whole vibe πŸŽ€


🌸 SYNOPSIS

here's the whole enum, no cap, exactly as it lives:

enum iommu_hw_info_arm_smmuv3_flags {
    IOMMU_HW_INFO_ARM_SMMUV3_ERRATA_REPEAT_TLBI_CFGI

};

yes it's a one-member enum and honestly? she's iconic for it πŸ’…


✨ Constants

  • IOMMU_HW_INFO_ARM_SMMUV3_ERRATA_REPEAT_TLBI_CFGI β€” okay so if this flag is set, user space has to issue TLBI/CFGI+SYNC commands twice 😭 because of a hardware erratum with the very cursed name T264-SMMU-3. like, not once. twice. the hardware said "do it again" and we simply must obey. you can read the full lore in the description at arm_smmu_erratum_repeat_tlbi_cfgi_key 🫢
ngl if you skip the double-issue you're in erratum territory and that is NOT the vibe check you want to fail πŸ’€

πŸ¦‹ SEE ALSO

the whole friend group πŸ’– β€” every single one, here we go:

  • Kernel file ./include/uapi/linux/iommufd.h
  • General ioctl format(9)
  • 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)
  • enum iommufd_option_ops(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)
  • 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, that's the entire group chat and yes i tagged everyone πŸ’€πŸ’–


that's the whole page bestie!! 🧚 source lives at ./include/uapi/linux, dated October 2026, and this little beauty is page enum iommu_...smmuv3_flags(9) from the Kernel API Manual β€” go forth and double-issue those TLBI/CFGI+SYNC commands, mwah πŸ’‹πŸŒˆβ­

πŸ“¦ where this page comes from