kvm_gpc_activate_hva(9)

📦 version 7.3.1, in nixpkgs unstable

💖 kvm_gpc_activate_hva 💖

okay so bestie, welcome to kvm_gpc_activate_hva — that's section 9 of the Kernel API Manual, and it's the iconic little helper that prepares a cached kernel mapping and an HPA for a given HVA. yes, that's a lot of acronyms, but we're gonna get through it together, i promise 🫶

✨ SYNOPSIS ✨

int kvm_gpc_activate_hva (struct gfn_to_pfn_cache *gpc , unsigned long
hva , unsigned long len );

like, that's the whole vibe. three args, one int coming back at you 💅

🌸 ARGUMENTS 🌸

  • gpc — your struct gfn_to_pfn_cache object. this is the main character of the operation, no cap.
  • hva — the userspace virtual address to map. yep, userspace. we're doing address translation things.
  • len — a sanity check, bestie! the range being access must fit a single page. that's literally its whole job.

🎀 RETURN 🎀

  • 0 — success! slay, we ate, everything worked 💖
  • -EINVAL — for a mapping which would cross a page boundary. so like, if you tried to be a little too ambitious with your range, this is the vibe check failing 😭
  • -EFAULT — for an untranslatable guest physical address. it's giving "can't translate that, sorry" 💀

🦋 DESCRIPTION 🦋

so the semantics of this function are the same as those of kvm_gpc_activate. same energy, same behaviour, nothing new to learn there, iykyk.

the one (1) difference? it merely bypasses a layer of address translation. that's it. that's the whole flex. lowkey elegant, highkey useful ✨

🌈 SEE ALSO 🌈

ngl bestie, go read the friends of this function too — they're all in the ./include/linux directory and they all live in the same era okay 🧚

and that's the page!! congrats, you're now fluent in HVA-to-HPA mapping discourse 🎓💜 this little gem lives in ./include/linux and the version date on it is October 2026 — so mark your calendars, screenshot it, whatever, because it's iconic and it's staying 💅🌸 see you in the next man page, bestie!! 🦋👑

📦 where this page comes from