STRUCT IOMMU_HWPT_VTD_S1_INVALIDATE(9)

💅 struct iommu_hwpt_vtd_s1_invalidate(9) 💅

okay bestie, welcome to the Kernel API Manual page for struct iommu_hwpt_vtd_s1_invalidate — it’s giving Intel VT-d cache invalidation, and the data type is IOMMU_HWPT_INVALIDATE_DATA_VTD_S1. ✨

✨ NAME ✨

struct iommu_hwpt_vtd_s1_invalidate — Intel VT-d cache invalidation (IOMMU_HWPT_INVALIDATE_DATA_VTD_S1).

🦋 SYNOPSIS 🦋

struct iommu_hwpt_vtd_s1_invalidate {
    __aligned_u64 addr;
    __aligned_u64 npages;
    __u32 flags;
    __u32 __reserved;
};

🎀 Members 🎀

• addr — The start address of the range to be invalidated. It needs to be 4KB aligned. 📏
• npages — Number of contiguous 4K pages to be invalidated.
• flags — Combination of enum iommu_hwpt_vtd_s1_invalidate_flags.
• __reserved — Must be 0. No cap, just zero. 🫶

🌸 Description 🌸

Okay so this is the Intel VT-d specific invalidation data for user-managed stage-1 cache invalidation in nested translation. Userspace uses this structure to tell the impacted cache scope after modifying the stage-1 page table. 💅

If you wanna invalidate all the caches related to the page table, set addr to 0 and npages to U64_MAX. That’s the whole-scope slay. 🔥

The device TLB will be invalidated automatically if ATS is enabled. No extra steps, bestie. 🧚

💜 SEE ALSO 💜

• 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)
• 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_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 page lives under ./include/uapi/linux, dated October 2026, and the footer spells the name as struct iomm...1_invalidate(9) — periodt. Byeee 🫶