DECLARE_IDTENTRY(9)

📦 version 7.3.1, in nixpkgs unstable

💅 DECLARE_IDTENTRY 💅

ok so bestie, real talk: this is a page from the Kernel API Manual (section 9), and it's all about DECLARE_IDTENTRY — like, the macro that declares functions for simple IDT entry points where no error code is pushed by hardware. That's the whole vibe. No error code. Clean entry. Slay.

✨ SYNOPSIS ✨

DECLARE_IDTENTRY (vector , func );

that's it, that's the whole call. two args, no drama 🎀

🫶 ARGUMENTS 🫶

  • vector — the vector number. and yes, it's ignored for C — like, C just does not care, ok? 🙈
  • func — the function name of the entry point. this is the name everything else gets built out of, so pick a good one bestie 💖

🌸 DESCRIPTION 🌸

okay so this macro declares four functions. four. count 'em:

  • the ASM entry point: asm_##func ⚡
  • the XEN PV trap entry point: xen_##func (maybe unused 👀)
  • the C handler called from the FRED event dispatcher (maybe unused 👀)
  • the C handler called from the ASM entry point

and that's the whole lineup. it's giving "small macro, big responsibilities" ngl 🔥

⭐ NOTE ⭐

lowkey important: this is the C variant of DECLARE_IDTENTRY. like the name literally says, it declares the entry points for usage in C code. and there's an ASM variant too — that one is what gets used to emit the entry stubs in entry_32/64.S. two different jobs, two different macros, don't mix them up bestie 😭

🦋 SEE ALSO 🦋

(and yes, the last two are listed twice in the original — i'm not gonna gaslight you and pretend otherwise, that's just how it is 💀)

ok that's the page!! this one comes from ./arch/x86/include/asm, dated October 2026, and it's filed under DECLARE_IDTENTRY(9) — go forth and declare your entry points, bestie, you got this 👑💜

📦 where this page comes from