mmap_action_simple_ioremap(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… mmap_action_simple_ioremap β€” from the Kernel API Manual, bestie

okay so picture this: you're hanging out in the kernel API manual, just vibing, and a page called mmap_action_simple_ioremap(9) shows up. that's our girl. she's a helper. she does one thing and she does it iconically. ✨


🌸 NAME 🌸

mmap_action_simple_ioremap β€” she's the helper for the mmap_prepare hook, and her whole job is to say "hey, this physical range right here, the one in [start_phys_addr, start_phys_addr + size), should get I/O remapped." that's it. that's the whole vibe. no cap. πŸ’–


πŸŽ€ SYNOPSIS πŸŽ€

void mmap_action_simple_ioremap (struct vm_area_desc *desc , phys_addr_t
start_phys_addr , unsigned long size );

look at her. void return, three arguments, zero drama. slay. πŸ”₯


πŸ¦‹ ARGUMENTS πŸ¦‹

okay bestie, here's what you're feeding her:

  • desc β€” the VMA descriptor for the VMA that's asking for the remap. she knows exactly which one, she's not confused, she's not guessing. πŸ‘‘
  • start_phys_addr β€” where the physical memory you want mapped actually starts. the beginning. the origin story. ⭐
  • size β€” how big the area to map is. the range is [start_phys_addr, start_phys_addr + size), so like, mind the bracket, she's watching. πŸŽ€

⚠️ NOTE ⚠️

some drivers out there might want to tweak desc->page_prot for write-combine purposes or something similar. that's valid. that's their moment. do your thing, driver. πŸ’…


🌈 SEE ALSO 🌈

she runs with a whole crowd, and honestly? the friend group is giving main character energy. the kernel file is ./include/linux/mm.h, and here's everybody else:

like, fifty-plus besties. she's connected. iykyk. 🫢


and that's the page, bestie πŸ’œ this one lives over in ./include/linux and the version floating around out there is dated October 2026 β€” go off, mmap_action_simple_ioremap(9), you ate. πŸ‘‘βœ¨πŸŒΈ

πŸ“¦ where this page comes from