is_eva_access(9)

🌸 NAME 🌸

okay bestie, welcome to the Kernel API Manual — the page we're reading is is_eva_access(9), and she's here to tell you whether an instruction is an EVA memory accessor. 💅

✨ SYNOPSIS ✨

bool is_eva_access (union mips_instruction inst );

🎀 ARGUMENTS 🎀

• inst — a 32-bit instruction encoding. that's the raw instruction vibe we're checking, no cap. 🦋

🔥 DESCRIPTION 🔥

So is_eva_access finds whether inst encodes an EVA memory access instruction. If it does, that's a whole signal that emulation of it should access the user mode address space instead of the kernel mode address space. This matters for MUSUK segments, which are TLB mapped for user mode but unmapped for kernel mode. literally the TLB plot twist. 😭

💖 RETURN 💖

It returns whether inst encodes an EVA accessor instruction. simple, iconic, to the point. ✨

🌈 SEE ALSO 🌈

The kernel file on deck is ./arch/mips/kvm/vz.c, and these related pages are all in the group chat:

• kvm_vz_should_use_htimer(9)
• _kvm_vz_restore_stimer(9)
• _kvm_vz_restore_htimer(9)
• kvm_vz_restore_timer(9)
• kvm_vz_acquire_htimer(9)
• _kvm_vz_save_htimer(9)
• kvm_vz_save_timer(9)
• kvm_vz_lose_htimer(9)
• is_eva_am_mapped(9)
• kvm_vz_gva_to_gpa(9)
• kvm_vz_badvaddr_to_gpa(9)
• kvm_trap_vz_handle_cop_unusable(9)
• kvm_trap_vz_handle_msa_disabled(9)
• kvm_vz_resize_guest_vtlb(9)

mwah 💋 — the source/version spot is ./arch/mips/kvm, the date is October 2026, and the title is is_eva_access(9). slay. 🫶