DEFINE_IDTENTRY_SYSVEC(9)

📦 version 7.3.1, in nixpkgs unstable

💅 DEFINE_IDTENTRY_SYSVEC(9) — a Kernel API Manual moment 🎀

okay bestie, gather round, because this one is literally from the Kernel API Manual and it's giving "low-level x86 interrupt lore" and honestly? obsessed. 🦋

✨ NAME ✨

DEFINE_IDTENTRY_SYSVEC — the macro that emits code for system vector IDT entry points. no cap, that's the whole vibe. 👑

🌸 SYNOPSIS 🌸

DEFINE_IDTENTRY_SYSVEC (func );

🎀 ARGUMENTS 🎀

  • func — the function name of the entry point. that's it. that's the arg. main character energy, honestly. 💖

🔥 DESCRIPTION 🔥

okay so here's the tea 🍓 — before the function body even gets to do its thing, irqentry_enter/exit and irq_enter/exit_rcu are invoked. like, they go first, periodt.

also, the KVM L1D flush request is set. yep. it's set. iconic behavior. 💅

and if the entry hit kernel mode, it runs the function on the interrupt stack. ✨ (that's the conditional, bestie — kernel mode hit = interrupt stack, iykyk.)

🌈 SEE ALSO 🌈

like, go read these too, fr fr — they're all in the kernel file ./arch/x86/include/asm/idtentry.h:

(yes, DECLARE_IDTENTRY_DF(9) and DEFINE_IDTENTRY_DF(9) show up twice in that list — that's exactly how the original rolls, so we're keeping it, don't come for me 🙈)

💀 reminder bestie: this is kernel-internal macro territory, so the details above are the whole story — nothing extra, nothing invented. 🫶

and that's a wrap, babe! this lil page lives under ./arch/x86/include/asm and it's dated October 2026, brought to you by the Kernel API Manual — slay, bye! 💜🧚‍♀️⭐

📦 where this page comes from