CALL_ARGS(9)

💅 CALL_ARGS(9) — like, the Kernel API Manual, bestie

okay so this one lives in the Kernel API Manual and it's genuinely one of those little macro gremlins that makes the preprocessor behave. stick with me, it's cute once you get it 🫶

---

✨ NAME ✨

CALL_ARGS — invoke a macro, but let its parameters get expanded before the call happens. yes, that's the whole vibe. no cap.

---

🌸 SYNOPSIS 🌸

CALL_ARGS (f , args... );

---

🎀 ARGUMENTS 🎀

• f — the name of the macro you wanna invoke. just the name, babe, not the whole call.
• args — the arguments you're feeding to that macro.

---

🦋 DESCRIPTION 🦋

so here's the tea ☕ — this macro is for calling macros whose names might be generated on the fly, or when you just really need to make sure the arguments get correctly expanded first. it's giving "trust the process, but verify the expansion" energy. periodt.

---

💖 EXAMPLE 💖

#define foo     X,Y,Z,Q
#define bar     COUNT_ARGS(foo)
#define buz     CALL_ARGS(COUNT_ARGS, foo)

with the definitions above, bar expands to 1 while buz expands to 4. and that difference? iconic. that's literally the whole point — CALL_ARGS expands foo into X,Y,Z,Q first, so COUNT_ARGS actually sees four args instead of one lump. slay 💅

---

🌈 SEE ALSO 🌈

• kernel file ./drivers/gpu/drm/xe/xe_args.h — go read it, iykyk 👀
• DROP_FIRST_ARG(9)
• FIRST_ARG(9)
• LAST_ARG(9)
• PICK_ARG(9)
• IF_ARGS(9)
• ARGS_SEP_COMMA(9)

all the arg-macro girlies, a whole friend group fr fr 💜

---

ngl bestie, these are preprocessor macros — the details of expansion order matter a lot, so don't be out here guessing. read the header, run it, confirm it. 🔥

---

and that's the page!! shipped from ./drivers/gpu/drm/xe, dated October 2026, and it ate, no crumbs left. mwah 🌸✨💖