INTERRUPT HANDLING(9)

💅 Interrupt Handling(9) 💅

okay so bestie, welcome to the Kernel API Manual — this one's from the interrupt side of the GPU world and it's genuinely iconic, let me tell you everything 🫶

✨ Interrupt Handling ✨

so like, picture this: interrupts get generated inside the GPU hardware itself, right? those raise what we call interrupt requests, and those get passed over to the amdgpu IRQ handler. and what does that handler do? literally its whole job — it detects the source and the type of the interrupt, and then it dispatches the matching handlers. main character energy, honestly 👑

but here's the tea 🍵 — if handling an interrupt means you gotta call kernel functions that might sleep, then the processing gets dispatched off to work handlers instead. no sleeping on the job, periodt.

and also — if MSI functionality is not disabled by the module parameter, then MSI support will be enabled. that's just how it is 💁‍♀️

last thing: for GPU interrupt sources that might be driven by another driver, IRQ domain support is what gets used (with mapping between virtual and hardware IRQs). iykyk 🌈

🌸 SEE ALSO 🌸

• kernel file ./drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c — go read it bestie, it's right there
• amdgpu_irq_disable_all(9)
• amdgpu_irq_handler(9)
• amdgpu_irq_handle_ih1(9)
• amdgpu_irq_handle_ih2(9)
• amdgpu_irq_handle_ih_soft(9)
• amdgpu_msi_ok(9)
• amdgpu_irq_init(9)
• amdgpu_irq_fini_sw(9)
• amdgpu_irq_add_id(9)
• amdgpu_irq_dispatch(9)
• amdgpu_irq_delegate(9)
• amdgpu_irq_update(9)
• amdgpu_irq_gpu_reset_resume_helper(9)
• amdgpu_irq_get(9)
• amdgpu_irq_put(9)
• amdgpu_irq_enabled(9)
• amdgpu_irqdomain_map(9)
• amdgpu_irq_add_domain(9)
• amdgpu_irq_remove_domain(9)
• amdgpu_irq_create_mapping(9)

okay that's the whole page, you ate that 💅✨ mwah 🎀

💖 sourced from ./drivers/gpu/drm/amd/amdgpu • dated October 2026 • see you in the next manpage bestie 💖