ENUM IOMMUFD_PAGE_RESPONSE_CODE(9)

💖 enum iommufd_page_response_code(9) 💖

okay so bestie, welcome to the Kernel API Manual, and today's main character is enum iommufd_page_response_code. yes, it's an enum, yes it only has two members, and yes it's still iconic. it's basically the little note you pass back to the IOMMU saying "k, handled it" or "nope, couldn't, don't bother retrying" 🫶

---

✨ NAME ✨

enum iommufd_page_response_code — Return status of fault handlers 💅

---

🦋 SYNOPSIS 🦋

enum iommufd_page_response_code {
    IOMMUFD_PAGE_RESP_SUCCESS ,
    IOMMUFD_PAGE_RESP_INVALID

};

---

🎀 CONSTANTS 🎀

okay so there's literally two of them, no cap, and they're doing very different things:

• IOMMUFD_PAGE_RESP_SUCCESS — slay, it worked! The fault has been handled and the page tables populated, so go ahead and retry the access 🔥 This is the "Success" defined in PCI 10.4.2.1.
• IOMMUFD_PAGE_RESP_INVALID — oof, we can't. Could not handle this fault, so don't retry the access 💀 This is the "Invalid Request" in PCI 10.4.2.1.

ngl bestie, those two constants are the whole enum. tiny but mighty. 🧚

---

🌈 SEE ALSO 🌈

the kernel file lives at ./include/uapi/linux/iommufd.h — and here's the entire friend group, fr fr, every single one, no skips:

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

---

and that's the whole vibe check, bestie 💜 this page ships from ./include/uapi/linux and it's dated October 2026 — so like, future iconic. go read the other ones too, iykyk 👑✨🌸