ENUM IOMMU_VEVENTQ_FLAG(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

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

okay so bestie, welcome to the Kernel API Manual ✨ this is the page for enum iommu_veventq_flag β€” yes that's a whole mouthful, we're doing it, stay with me 🫢


🌸 NAME 🌸

enum iommu_veventq_flag β€” literally just the flag for struct iommufd_vevent_header, no cap πŸ’–


✨ SYNOPSIS ✨

enum iommu_veventq_flag {
    IOMMU_VEVENTQ_FLAG_LOST_EVENTS

};

look at her. one (1) member. main character energy πŸ‘‘


πŸŽ€ Constants πŸŽ€

  • IOMMU_VEVENTQ_FLAG_LOST_EVENTS β€” the vEVENTQ has lost vEVENTs 😭 that's it, that's the whole vibe. events went missing. gone. not me crying about dropped vEVENTs πŸ’€

πŸ¦‹ SEE ALSO πŸ¦‹

okay this list is long long, but every single one of these is iconic in her own way, so here we go, no skipping, i promised 🫢

Kernel file ./include/uapi/linux/iommufd.h β€” start here bestie, that's the source of truth ✨

then the whole fam:

  • 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)
  • 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)
  • 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)

that's sixty-one entries and yes i counted, we don't do half measures here πŸ’…πŸ”₯

also heads up: this page lives under ./include/uapi/linux and it's dated October 2026, so like… future vibes 🌈

and that's the whole page bestie, you ate that πŸ“ stay hydrated, read your headers, and remember: if IOMMU_VEVENTQ_FLAG_LOST_EVENTS is set, the vEVENTQ has lost vEVENTs and you should probably go look at that πŸ™ˆπŸ’œ

β€” sign-off from your girl in ./include/uapi/linux, October 2026, version of the Kernel API Manual πŸŽ€πŸ«Άβœ¨

πŸ“¦ where this page comes from