alloc_irq_cpu_rmap(9)
β¨ alloc_irq_cpu_rmap π
okay so this is from the Kernel API Manual (that's the 9 section bestie, kernel dev territory π) and it's literally the page for alloc_irq_cpu_rmap β the function that allocates a CPU affinity reverse-map for IRQs. yes that's a whole mouthful, we'll get to it π«Ά
πΈ NAME πΈ
alloc_irq_cpu_rmap β allocate CPU affinity reverse-map for IRQs β¨
no cap, that's the whole vibe: you're building the reverse-map so you can go from an IRQ back to the CPUs that are down with it π
π SYNOPSIS π
struct cpu_rmap * alloc_irq_cpu_rmap (unsigned int size );
it hands you back a struct cpu_rmap * pointer, and you feed it one unsigned int size. that's the whole signature, iconic and simple π
π¦ ARGUMENTS π¦
sizeβ Number of objects to be mapped. literally that many things getting mapped, so like, pick your number wisely bestie π
π₯ DESCRIPTION π₯
so here's the thing β Must be called in process context. periodt. not interrupt context, not some random atomic corner, process context only. the way this is a hard requirement and not a suggestion π take it seriously fr fr π
π SEE ALSO π
- Kernel file
./include/linux/cpu_rmap.hβ the header where all this lives, go read it, it's giving source of truth π struct cpu_rmap(9)β the struct itself, the main character of this whole story π
π lowkey reminder: size = number of objects to be mapped, and process context is non-negotiable. that's it, that's the page πβ¨
and that's a wrap bestie!! π this lil page comes to you from ./include/linux, dated October 2026 β mwah, go map those IRQs, you're gonna slay ππ§ββοΈβ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms