ENUM IOMMU_PAGE_RESPONSE_CODE(9)

💅 enum iommu_page_response_code(9) 💅

okay bestie, welcome to the enum iommu_page_response_code(9) glow-up — this is straight out of the Kernel API Manual and honestly? it's giving "small but mighty". no cap. 🦋

---

✨ NAME ✨

enum iommu_page_response_code — the return status of fault handlers. literally just the vibe report your IOMMU sends back after it handles (or doesn't handle) a page fault. 🎀

---

🌸 SYNOPSIS 🌸

enum iommu_page_response_code {
    IOMMU_PAGE_RESP_SUCCESS ,
    IOMMU_PAGE_RESP_INVALID ,
    IOMMU_PAGE_RESP_FAILURE

};

look at her. three constants, zero drama. main character energy fr fr. 👑

---

🌈 Constants 🌈

• IOMMU_PAGE_RESP_SUCCESS — the fault has been handled and the page tables populated, so go ahead and retry the access 💖. this one is "Success" in PCI PRI. we love a happy ending.
• IOMMU_PAGE_RESP_INVALID — nope, couldn't handle this fault, so don't retry the access 🙈. this one is "Invalid Request" in PCI PRI. it's giving "not my problem" but politely.
• IOMMU_PAGE_RESP_FAILURE — general error 😭. drop all subsequent faults from this device if possible. this one is "Response Failure" in PCI PRI. lowkey the worst one to get tbh.

bestie pls note: IOMMU_PAGE_RESP_FAILURE isn't a one-page oopsie — it's telling you to drop all subsequent faults from this device if possible. that's a whole-device vibe check failing. handle with care. 💀

---

🫶 SEE ALSO 🫶

Kernel file ./include/linux/iommu.h plus this entire friend group:

• struct iommu_fault_page_request(9)
• struct iommu_fault(9)
• struct iommu_page_response(9)
• struct iopf_queue(9)
• struct iommu_resv_region(9)
• struct iommu_iotlb_gather(9)
• struct iommu_dirty_bitmap(9)
• struct iommu_dirty_ops(9)
• struct iommu_user_data(9)
• struct iommu_user_data_array(9)
• __iommu_copy_struct_from_user(9)
• iommu_copy_struct_from_user(9)
• __iommu_copy_struct_from_user_array(9)
• iommu_copy_struct_from_user_array(9)
• iommu_copy_struct_from_full_user_array(9)
• __iommu_copy_struct_to_user(9)
• iommu_copy_struct_to_user(9)
• struct iommu_ops(9)
• struct iommu_domain_ops(9)
• struct iommu_device(9)
• struct iommu_fault_param(9)
• struct dev_iommu(9)
• iommu_iotlb_gather_is_disjoint(9)
• iommu_iotlb_gather_add_range(9)
• iommu_iotlb_gather_add_page(9)
• struct iommu_fwspec(9)
• struct iommu_sva(9)
• iommu_map_sgtable(9)

that's a lot of mutuals, but they all live together in ./include/linux so it tracks. 💜

---

and that's the whole page, bestie — no crumbs left. this icon dropped in October 2026, lives in ./include/linux, and answers to the name enum iommu_...esponse_code(9) in the Kernel API Manual. periodt. 💅✨🌸