ENUM IOMMU_HWPT_VTD_S1_INVALIDATE_FLAGS(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ enum iommu_hwpt_vtd_s1_invalidate_flags(9) ✨

okay so this is a page from the Kernel API Manual, and it's literally just one tiny enum β€” like, one flag, one single icon flag, and yet the SEE ALSO section is a whole friend group πŸ’€. Anyway bestie, let's get into it.


🌸 NAME 🌸

enum iommu_hwpt_vtd_s1_invalidate_flags β€” the flags you pass for Intel VT-d stage-1 cache invalidation. that's it, that's the vibe πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

here's the whole thing, look how small she is:

enum iommu_hwpt_vtd_s1_invalidate_flags {
    IOMMU_VTD_INV_FLAGS_LEAF

};

πŸ’… Constants πŸ’…

  • IOMMU_VTD_INV_FLAGS_LEAF β€” this one tells you whether the invalidation applies to the all-levels page structure cache or just the leaf PTE cache. so basically: are we nuking the whole tree or just the leaf? iykyk 🌈

πŸ”₯ SEE ALSO πŸ”₯

first up, the source of truth, the main character herself: kernel file ./include/uapi/linux/iommufd.h πŸ’–

and now the whole squad, in order, no cap β€” 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), 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), 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 a lot of friends and every single one of them ate πŸ’…βœ¨


and that's the whole page bestie, short and sweet πŸ“ β€” sourced from ./include/uapi/linux, dated October 2026, with the manual page name being enum iommu_...lidate_flags(9) (yes the title got clipped, she's mysterious like that πŸ™ˆ). mwah, go read your errno docs, ily πŸ«ΆπŸ’œ

πŸ“¦ where this page comes from