kvm_vz_guest_tlb_lookup(9)

📦 version 7.3.1, in nixpkgs unstable

💫 kvm_vz_guest_tlb_lookup(9) 💫

ok so this is a page from the Kernel API Manual and honestly? it's a little baddie. it does exactly one thing and it does it well, no notes. let's get into it bestie 🎀

🌸 NAME 🌸

kvm_vz_guest_tlb_lookup — literally just looks up a guest VZ TLB mapping. that's the whole vibe. 💅

✨ SYNOPSIS ✨

int kvm_vz_guest_tlb_lookup (struct kvm_vcpu *vcpu , unsigned long gva ,
       unsigned long *gpa );

yes the spacing is like that in the original, we don't touch it, we respect the ancestors 🫶

🦋 ARGUMENTS 🦋

  • vcpu — your KVM VCPU pointer. the main character of this whole situation 👑
  • gva — the original manpage says -- undescribed -- and honestly? iconic. mysterious. unbothered. no cap, it's giving "we ran out of time to write the docs" 😭 (it's the guest virtual address, iykyk — but fr the page doesn't say, so i'm not gonna pretend it does)
  • gpa — a pointer to the output guest physical address, like, whatever gva maps to. that's where the answer goes 💖

💜 DESCRIPTION 💜

so what does it actually DO. it converts a guest virtual address — one that lives in a guest TLB mapped segment — into a guest physical address. how? by probing the guest TLB. that's it. that's the tea ☕

lowkey elegant. highkey obsessed. ✨

🔥 RETURN 🔥

two possible outcomes, bestie, and you gotta know which one you're in:

  • 0 — a guest TLB mapping exists for gva. slay! *gpa will have been written. 💖
  • -EFAULT — no guest TLB mapping exists for gva. sad trombone 💀 and heads up: *gpa may not have been written. not "wasn't" — may not. so don't go reading it and acting surprised, okay? 🙈

🌈 SEE ALSO 🌈

the kernel file ./arch/mips/kvm/tlb.c is out here with a whole friend group:

go read them, they're all in their TLB era 🧚

and that's the page!! brought to you by ./arch/mips/kvm, dated October 2026 — time traveler behavior honestly, we love to see it ⭐💅 bye bestie, go probe that TLB 🍓

📦 where this page comes from