create_hyp_exec_mappings(9)

✨ create_hyp_exec_mappings(9) ✨

okay so this is a page straight out of the Kernel API Manual, section 9, and it's literally about mapping an executable range into HYP 💅 like yes we're doing hypervisor things today bestie

---

🎀 NAME 🎀

create_hyp_exec_mappings — map an executable range into HYP, no cap 🫶

---

🌸 SYNOPSIS 🌸

int create_hyp_exec_mappings (phys_addr_t phys_addr , size_t size , void
       **haddr );

it's giving "three arguments, one return value, all business" ✨

---

🦋 ARGUMENTS 🦋

• phys_addr — the physical start address that gets mapped 💖 this is where the region actually lives
• size — size of the region being mapped, like how much of it we're doing
• haddr — HYP VA for this mapping ⭐ (the virtual address on the HYP side, and it comes back through the pointer)

---

🌈 SEE ALSO 🌈

the whole friend group fr fr, go check them out:

• Kernel file ./arch/arm64/kvm/mmu.c
• 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)
• 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 whole page bestie, short and iconic 💜

source: ./arch/arm64/kvm · dated October 2026 · filed under create_hyp_exec_mappings(9) — mwah, take care, go map something 🧚‍♀️🔥