STRUCT IOMMU_IOVA_RANGE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– struct iommu_iova_range(9) β€” Kernel API Manual πŸ’–

okay so bestie, this is the struct iommu_iova_range(9) page from the Kernel API Manual, and it's literally the ioctl(IOMMU_IOVA_RANGE) struct. It's tiny, it's iconic, and it's about to make sense. 🫢

πŸ’– NAME πŸ’–

struct iommu_iova_range β€” ioctl(IOMMU_IOVA_RANGE). That's the whole name, and yes, it ate. ✨

🌈 SYNOPSIS 🌈

Here's the struct in all its tiny glory:

struct iommu_iova_range {
    __aligned_u64 start;
    __aligned_u64 last;
};

πŸŽ€ Members πŸŽ€

  • start β€” First IOVA. The opening act, the main character's entrance. πŸ‘‘
  • last β€” Inclusive last IOVA. Inclusive is the key word, bestie β€” the last IOVA is included in the interval. πŸ’…

πŸ¦‹ Description πŸ¦‹

An interval in IOVA space. That's it. That's the vibe. It's giving "simple struct, big purpose" energy. 🌸

✨ SEE ALSO ✨

You already know we gotta shout out the kernel file and the whole friend group of related manpages. Go read these next, bestie:

  • Kernel file ./include/uapi/linux/iommufd.h
  • General ioctl format(9)
  • struct iommu_destroy(9)
  • struct iommu_ioas_alloc(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)
  • 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)

mwah πŸ’‹ this lil page comes from ./include/uapi/linux, dated October 2026, and it's the struct iommu_iova_range(9) manual page. periodt. 🌟

πŸ“¦ where this page comes from