ENUM IOMMUFD_HWPT_GET_DIRTY_BITMAP_FLAGS(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… enum iommufd_hwpt_get_dirty_bitmap_flags(9) πŸ’…

ok so this is a page from the Kernel API Manual β€” yes bestie, the Kernel API Manual, and it's about enum iommufd_hwpt_get_dirty_bitmap_flags, which is literally just the flag bucket for getting dirty bits. that's the whole vibe. 🫢


✨ NAME ✨

enum iommufd_hwpt_get_dirty_bitmap_flags β€” the flags you use when you're getting dirty bits πŸŽ€


🌸 SYNOPSIS 🌸

enum iommufd_hwpt_get_dirty_bitmap_flags {
    IOMMU_HWPT_GET_DIRTY_BITMAP_NO_CLEAR

};

yeah that's it, that's the whole enum. one (1) flag. icon behavior honestly πŸ‘‘


πŸ¦‹ Constants πŸ¦‹

  • IOMMU_HWPT_GET_DIRTY_BITMAP_NO_CLEAR β€” okay so this one is the "look but don't touch" flag πŸ’… it just reads the PTEs and does not clear any of the dirty bits metadata. no cap, nothing gets wiped. and the reason you'd pass it is when you're expecting your next operation to be an unmap of the same IOVA range β€” so like, you're peeking now because you already know the teardown is coming. iykyk πŸ”₯

πŸ‘‘ SEE ALSO πŸ‘‘

bestie, buckle up, this cross-reference list is long β€” but every single one of these is part of the family so we're listing them all πŸ’–

The kernel file you want is ./include/uapi/linux/iommufd.h, and then there's:

  • 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)
  • 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, sixty entries. sixty. and we kept every single one because that's what besties do 🧚


lowkey a reminder that this is kernel UAPI territory β€” it's the interface, so treat those names like they're sacred. don't be out here renaming things πŸ™ˆ

🌈 okay that's the page!! this one lives under ./include/uapi/linux, dated October 2026, and it's part of the Kernel API Manual β€” mwah, go read the source, ily, bye πŸ’œπŸ’…

πŸ“¦ where this page comes from