DECLARE_IDTE...AW_ERRORCODE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… DECLARE_IDTENTRY_RAW_ERRORCODE β€” like, the whole vibe

okay so bestie, welcome to the DECLARE_IDTENTRY_RAW_ERRORCODE(9) page from the Kernel API Manual. yes that's a lot of capital letters, no I will not be apologizing. this is the x86 IDT entry point lore and it's honestly kind of iconic once you get it πŸŽ€


✨ NAME ✨

DECLARE_IDTENTRY_RAW_ERRORCODE β€” Declare functions for raw IDT entry points Error code pushed by hardware

like, that's the whole thing. it declares functions. for raw IDT entry points. and the error code is pushed by the hardware, not by you, so don't come for it πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

DECLARE_IDTENTRY_RAW_ERRORCODE (vector , func );

that's it. two things in, macro does its thing. slay.


🌸 ARGUMENTS 🌸

  • vector β€” Vector number (ignored for C). yeah bestie, it just gets ignored in C. not me showing up to the function call and being told I'm not needed 😭
  • func β€” Function name of the entry point. this one actually matters, it's the name your entry point function gets, so pick a good one 🫢

πŸ’– DESCRIPTION πŸ’–

so what does it actually do? it maps to DECLARE_IDTENTRY_ERRORCODE. that's the whole description. it's giving "short and mysterious main character energy" and honestly? we respect it πŸ‘‘


πŸ”₯ SEE ALSO πŸ”₯

the receipts live in the kernel file ./arch/x86/include/asm/idtentry.h, and here's the full friend group β€” every single one, no cap:

(yes, DECLARE_IDTENTRY_DF(9) and DEFINE_IDTENTRY_DF(9) are both in there twice. we're keeping them. periodt. πŸ’€)


and that's the page, bestie!! 🧚 go forth and declare your raw error-code entry points, you absolute icon 🌈⭐

source file: ./arch/x86/include/asm  Β·  dated October 2026  Β·  and yes that's DECLARE_IDTE...AW_ERRORCODE(9) in the footer because the terminal truncates it and we love that for it πŸ’œ

πŸ“¦ where this page comes from