imr_add_range(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– imr_add_range(9) πŸ’–

okay so this is the Kernel API Manual entry for imr_add_range(9), and bestie, it's giving β€œsmall function, very specific job.” Here's the whole thing, no cap. πŸŽ€

✨ NAME ✨

imr_add_range β€” add an Isolated Memory Region.

🌸 SYNOPSIS 🌸

int imr_add_range (phys_addr_t base , size_t size , unsigned int rmask ,
       unsigned int wmask );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • base β€” physical base address of region aligned to 1KiB.
  • size β€” physical size of region in bytes must be aligned to 1KiB.
  • rmask β€” read access mask.
  • wmask β€” write access mask.

πŸ’… RETURN πŸ’…

It returns zero on success or a negative value indicating error. literally that's the whole vibe check. βœ…πŸ˜­

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file: ./arch/x86/platform/intel-quark/imr.c

and these other little icons:


okay that's the whole page, bestie! this little cutie lives at source path ./arch/x86/platform/intel-quark, dated October 2026, and it's the imr_add_range(9) manual page. mwah πŸ’‹βœ¨πŸ«Ά

πŸ“¦ where this page comes from