dm_test_irq_...okes_handler(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 dm_test_irq_...okes_handler(9) 🌸

okay so bestie, welcome to the Kernel API Manual β€” yes, that's the manual name, and yes, you're reading a manpage about a KUnit test πŸ’… this whole thing is a single test that checks whether immediate work actually calls its handler. no cap. it's giving "tiny test, huge SEE ALSO section" energy and honestly? iconic πŸŽ€


✨ NAME ✨

dm_test_irq_immediate_work_invokes_handler β€” a test that checks that immediate work calls the handler πŸ¦‹

like, that's literally the whole job. immediate work β†’ invokes handler. periodt.


πŸ’– SYNOPSIS πŸ’–

void dm_test_irq_immediate_work_invokes_handler (struct kunit *test );

that's it, that's the function signature, copy it exactly bestie β€” don't be out here "fixing" the spacing, it's fine, it's fine 🌸


🫢 ARGUMENTS 🫢

  • test β€” the KUnit test context πŸ‘‘ that's what gets passed in, and that's the only thing it takes. KUnit context, one (1) singular, no more, no less, fr fr.

πŸ”₯ SEE ALSO πŸ”₯

okay so this list is long and I'm obsessed 😭 but every single one goes in, because dropping any of them would be a crime against the group chat. first up, the file itself, then the whole extended test family:

Kernel file πŸ’€

./drivers/gpu/drm/amd/display/amdgpu_dm/tests/amdgpu_dm_irq_test.c

and now the crew, one per line, exactly as they appear:

πŸ’€ that's the whole list, all 120-ish of them, not one dropped. if you were thinking "surely she skipped a couple" β€” no ma'am, we don't do that here πŸ™ˆ

and that's the page bestie! 🧚 quick sign-off so you know where this came from: it's out of the kernel source tree at ./drivers/gpu/drm/amd/display/..., dated October 2026, and it's the dm_test_irq_...okes_handler(9) page from the Kernel API Manual. slay, go read dm_test_irq_immediate_work_empty(9) next, love that for you β­πŸ’œ

πŸ“¦ where this page comes from