mips_gic_vx_map_reg(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… mips_gic_vx_map_reg(9) β€” from the Kernel API Manual, bestie πŸ’–

okay so picture this: it's a kernel manual page, it's about MIPS GICs, and it's lowkey kind of a baddie. this is mips_gic_vx_map_reg, and we're gonna get you fluent in it ✨


🌸 NAME 🌸

mips_gic_vx_map_reg β€” returns the GIC_Vx_<intr>_MAP register offset. that's the whole job. she's a one-line icon πŸ‘‘


πŸ¦‹ SYNOPSIS πŸ¦‹

unsigned int mips_gic_vx_map_reg (enum mips_gic_local_interrupt intr );

πŸŽ€ ARGUMENTS πŸŽ€

  • intr β€” a GIC local interrupt. that's it, that's the whole argument. give her one (1) interrupt and she'll do the rest 🫢

πŸ’œ DESCRIPTION πŸ’œ

so what she actually does is determine the index of the GIC_VL_<intr>_MAP or GIC_VO_<intr>_MAP register inside the block of GIC map registers. like, she's the friend who knows exactly where everyone's sitting at the table πŸ’…

and here's the tea: it's almost the same order as the interrupts in the pending & mask registers β€” the one used by enum mips_gic_local_interrupt β€” BUT it moves the FDC interrupt, and because of that it offsets all the interrupts after it... 😭 so close to being identical and yet. not.

the return value is suitable for use with the (read|write)_gic_v[lo]_map accessor functions. so like, you get the index from her, you hand it straight to those accessors, and everything slays ✨


πŸ”₯ RETURN πŸ”₯

the map register index corresponding to intr. no cap, that's literally the whole return value πŸ‘‘


🌈 SEE ALSO 🌈


fr fr bestie, read the whole list. the FDC one especially β€” she's the reason the ordering shifts, remember? iykyk πŸ’€

and that's the page!! 🌟 this one lives in ./arch/mips/include/asm, dated October 2026 β€” mwah, go touch some registers, ily πŸ§šβ€β™€οΈπŸ’–πŸŽ€

πŸ“¦ where this page comes from