irq_reserve_ipi(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… irq_reserve_ipi(9) β€” Kernel API Manual

okay so bestie, welcome to irq_reserve_ipi, the function in the Kernel API Manual (section 9, we're doing kernel internals today πŸŽ€) that sets up an IPI to a destination cpumask. yes it's giving low-level, yes it's iconic, let's get into it ✨


✨ NAME ✨

irq_reserve_ipi β€” Setup an IPI to destination cpumask πŸ¦‹

🌸 SYNOPSIS 🌸

int irq_reserve_ipi (struct irq_domain *domain , const struct cpumask
*dest );

πŸ’– ARGUMENTS πŸ’–

  • domain β€” the IPI domain, bestie 🫢
  • dest β€” the cpumask of CPUs which can receive the IPI. like, the whole guest list of who's allowed to get this interrupt πŸ’Œ

πŸ‘‘ DESCRIPTION πŸ‘‘

So what it does is: it allocates a virq that can be used to send an IPI to any CPU in the dest mask. that's it, that's the whole vibe. one virq, and it's valid for every CPU hanging out in that mask πŸ’…βœ¨

πŸ”₯ RETURN πŸ”₯

On success you get the Linux IRQ number back. on failure? you get an error code. no cap, that's the deal πŸ’€

ngl bestie, always check the return value β€” success gives you an IRQ number, failure gives you an error code, and those are NOT the same thing πŸ™ˆ

🌈 SEE ALSO 🌈

Kernel file ./kernel/irq/ipi.c β€” go read it, it's right there πŸ’œ

all the IPI besties, together, the way it should be πŸ§šπŸ“


and that's the page fr fr πŸŽ€ it lives in ./kernel/irq and this version is dated October 2026, page irq_reserve_ipi(9) β€” mwah, slay, periodt πŸ’…πŸ’–

πŸ“¦ where this page comes from