create_hyp_io_mappings(9)

💅 create_hyp_io_mappings — from the Kernel API Manual, bestie ✨

okay so picture this: you're in the <rainbow>Kernel API Manual</rainbow> and you found this little icon. It's literally called create_hyp_io_mappings, and what it does is map IO into both kernel and HYP. That's it. That's the whole vibe. Two worlds, one mapping, main character energy 🫶

✨ SYNOPSIS ✨

int create_hyp_io_mappings (phys_addr_t phys_addr , size_t size , void
__iomem **kaddr , void __iomem **haddr );

she takes four things and returns an int, no cap 💖

🎀 ARGUMENTS 🎀

• phys_addr — the physical start address that gets mapped. like, where the actual hardware lives, periodt 📍
• size — size of the region being mapped. how much we're taking, bestie 📏
• kaddr — Kernel VA for this mapping. one address, for the kernel side 🌸
• haddr — HYP VA for this mapping. and the other one, for the HYP side 🦋

not me re-reading this like yes, both kaddr and haddr are pointers-to-pointers (void __iomem **) — that detail matters, don't @ me 💀

👑 SEE ALSO 👑

Kernel file ./arch/arm64/kvm/mmu.c — and also, the whole friend group, fr fr:

• kvm_arch_flush_remote_tlbs(9)
• __unmap_stage2_range(9)
• stage2_flush_vm(9)
• free_hyp_pgds(9)
• create_hyp_mappings(9)
• hyp_alloc_private_va_range(9)
• create_hyp_exec_mappings(9)
• kvm_init_stage2_mmu(9)
• stage2_unmap_vm(9)
• kvm_phys_addr_ioremap(9)
• kvm_stage2_wp_range(9)
• kvm_mmu_wp_memory_region(9)
• kvm_mmu_split_memory_region(9)
• kvm_handle_guest_abort(9)

and that's the page, bestie 💜 sourced from ./arch/arm64/kvm, dated October 2026 — iconic of her, honestly. go map some IO 🧚‍♀️✨