kvm_vcpu_exit_request(9)

✨ kvm_vcpu_exit_request ✨

okay bestie, welcome to the kvm_vcpu_exit_request page from the Kernel API Manual — yes that's the manual name, and yes it's giving "official but make it cute" 💅

This one's a little function that tells you whether the VCPU should not enter the guest, like, at all. Not today, guest. 🚪✨

---

🌸 SYNOPSIS 🌸

bool kvm_vcpu_exit_request (struct kvm_vcpu *vcpu , int *ret );

that's the whole signature, no cap — it takes two things and hands you back a bool 🫶

---

🎀 ARGUMENTS 🎀

• vcpu — the VCPU pointer, literally just the pointer to the VCPU we're vibing about 🦋
• ret — a pointer where the optional return code gets written. optional, bestie, remember that word 👀

---

🌈 RETURN 🌈

returns true if the VCPU needs to bail back to a preemptible + interruptible state and skip guest entry. that's the whole vibe check ✅

---

💖 DESCRIPTION 💖

so here's the tea, and it's actually iconic: this function disambiguates between two different types of exits 🧚

1. exits to a preemptible + interruptible kernel context
2. exits to userspace

for an exit to userspace, this function will write the return code to ret and return true. 🎯

for an exit to preemptible + interruptible kernel context — i.e. check for pending work and re-enter — it returns true without writing to ret. no touchy the ret, periodt 🚫💅

so if you're staring at ret wondering why nothing landed there: it might just be the second kind of exit. check before you assume, iykyk 😭

---

🦋 SEE ALSO 🦋

• Kernel file ./arch/arm64/kvm/arm.c — go read it, it's the main character here 👑
• kvm_arch_init_vm(9)
• kvm_arch_destroy_vm(9)
• kvm_arch_vcpu_runnable(9)
• kvm_vcpu_wfi(9)
• check_vcpu_requests(9)
• kvm_arch_vcpu_ioctl_run(9)

---

and that's the page fr fr 💜 this one lives in ./arch/arm64/kvm and it's dated October 2026 — so mark your calendar bestie, slay 🎀⭐💀