acpi_os_map_iomem(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

acpi_os_map_iomem β€” get a virtual address for a given physical address range. This is from the Kernel API Manual, and the page is literally acpi_os_map_iomem(9). Slay. πŸ’…


✨ SYNOPSIS ✨

void __iomem __ref * acpi_os_map_iomem (acpi_physical_address phys ,
acpi_size size );

πŸŽ€ ARGUMENTS πŸŽ€

  • phys β€” start of the physical address range to map. Like, the beginning of the range, bestie.
  • size β€” size of the physical address range to map. How much of the range we’re grabbing.

πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so here’s the vibe: it looks up the given physical address range in the list of existing ACPI memory mappings. If found, it gets a reference to it and returns a pointer to it β€” that pointer is its virtual address. If it’s not found, it maps it, adds it to that list, and returns a pointer to it. Iconic behavior, honestly. ✨

During early init β€” specifically when acpi_permanent_mmap has not been set yet β€” this routine simply calls __acpi_map_table to get the job done. No cap. 🫢


🌈 SEE ALSO 🌈


Source/version: ./drivers/acpi β€’ Date: October 2026 β€’ Page: acpi_os_map_iomem(9) β€” bye bestie, go map those ranges responsibly πŸ’…βœ¨

πŸ“¦ where this page comes from