guest_state_exit_irqoff(9)

💅 NAME 💅

okay so bestie, this is guest_state_exit_irqoff from the Kernel API Manual, and its whole personality is: establish state when returning from guest mode. that's the assignment. that's the vibe. ✨

✨ SYNOPSIS ✨

void guest_state_exit_irqoff (void );

🎀 ARGUMENTS 🎀

• void — no arguments. literally none. zero. empty set. 🫶

🦋 DESCRIPTION 🦋

okay so here's the lore: entry from a guest disables interrupts, but guest mode is traced as interrupts enabled. also, with NO_HZ_FULL, RCU might be idle. no cap. 😭

so this function does three little steps in order:

1. Tell lockdep that interrupts are disabled. 🎀
2. Invoke context tracking if enabled to reactivate RCU. 🔥
3. Trace interrupts off state. ⭐

It's invoked from architecture specific code after exiting a guest. and listen: it must be invoked with interrupts disabled, and the caller must be non-instrumentable. not optional, bestie. 💅 The caller also has to invoke guest_timing_exit_irqoff after this. yes, after. no skipping. 🙈

🌸 NOTE 🌸

this is analogous to enter_from_user_mode. iykyk. 🌈

⭐ SEE ALSO ⭐

the kernel file ./include/linux/kvm_host.h is right there, and the whole squad is:

• guest_state_enter_irqoff(9)
• kvm_gpc_init(9)
• kvm_gpc_activate(9)
• kvm_gpc_activate_hva(9)
• kvm_gpc_check(9)
• kvm_gpc_refresh(9)
• kvm_gpc_deactivate(9)
• kvm_stats_linear_hist_update(9)
• kvm_stats_log_hist_update(9)

okay that's the page, bestie! source/version: ./include/linux; date: October 2026; manual: guest_state_exit_irqoff(9). byeee and slay your interrupts responsibly 💖🦋🎀