kvm_handle_guest_abort(9)

💅 kvm_handle_guest_abort — the Kernel API Manual page, bestie edition ✨

okay so this is the manual page for kvm_handle_guest_abort from the Kernel API Manual, and it's literally the girlboss that handles all 2nd stage aborts 🫶

---

✨ NAME ✨

kvm_handle_guest_abort — handles all 2nd stage aborts 👑

🌸 SYNOPSIS 🌸

int kvm_handle_guest_abort (struct kvm_vcpu *vcpu );

like, that's the whole signature. short and iconic, no notes 💅

🎀 ARGUMENTS 🎀

• vcpu — the VCPU pointer. that's it. that's the whole argument. she takes one (1) VCPU pointer and minds her business 🦋

💖 DESCRIPTION 💖

okay so bestie, listen 👀 — any abort that gets all the way to the host is almost guaranteed to be caused by a missing second stage translation table entry. like, that's the vibe check it's failing, no cap.

and that missing entry can mean one of two things:

1. the guest simply needs more memory, and we must allocate an appropriate page 🍓
2. the guest tried to access I/O memory, which is emulated by user space 🧚

the way she tells them apart is based on the IPA causing the fault, and whether this memory region has been registered as standard RAM by user space ⭐ that's the whole distinction, periodt.

🔥 SEE ALSO 🔥

the kernel file ./arch/arm64/kvm/mmu.c is right there if you wanna go read it iykyk, and also go check out these icons:

• 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_phys_addr_ioremap(9)
• kvm_stage2_wp_range(9)
• kvm_mmu_wp_memory_region(9)
• kvm_mmu_split_memory_region(9)

---

and that's the page, bestie 🫶 this one came out of ./arch/arm64/kvm, dated October 2026 — mwah, slay, go read your aborts 💋🌈