kvm_phys_addr_ioremap(9)

💅 kvm_phys_addr_ioremap(9) — a Kernel API Manual moment

okay so bestie, this one lives in the Kernel API Manual and it's literally called kvm_phys_addr_ioremap — which is a whole mouthful, i know, but stay with me. It maps a device range to guest IPA. that's the whole vibe. 🎀

---

✨ NAME ✨

kvm_phys_addr_ioremap — map a device range to guest IPA 🦋

---

✨ SYNOPSIS ✨

int kvm_phys_addr_ioremap (struct kvm *kvm , phys_addr_t guest_ipa ,
phys_addr_t pa , unsigned long size , bool writable );

like, that's the signature, copy it exactly please, it's giving "don't touch the formatting" 😌

---

✨ ARGUMENTS ✨

• kvm — the KVM pointer. your main character struct, the whole reason we're here 👑
• guest_ipa — the IPA at which to insert the mapping. that's the address that's getting a little mapping-shaped home 🏠
• pa — the physical address of the device. the actual hardware, fr fr 🔥
• size — the size of the mapping. how much room it takes up, no cap 📏
• writable — whether or not to create a writable mapping. true = yes bestie you may write, false = look but don't touch 🙈

---

🌈 SEE ALSO 🌈

Kernel file ./arch/arm64/kvm/mmu.c — and honestly the whole friend group shows up here, so let me introduce you 💖:

• 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_io_mappings(9)
• create_hyp_exec_mappings(9)
• kvm_init_stage2_mmu(9)
• stage2_unmap_vm(9)
• kvm_stage2_wp_range(9)
• kvm_mmu_wp_memory_region(9)
• kvm_mmu_split_memory_region(9)
• kvm_handle_guest_abort(9)

like?? that's the entire group chat tagged in one post. iconique. iykyk 💅

---

okay that's the page!! sobbing a little, she's perfect 🫶

sign-off time, cuties: this gorgeous thing is brought to you from ./arch/arm64/kvm, dated October 2026 — that's the source/version and the date, so you know exactly when it was serving looks ⭐🧚‍♀️💜