STRUCT KVM_SMCCC_FEATURES(9)

🌸 NAME 🌸

struct kvm_smccc_features — bestie, it's literally the descriptor of the hypercall services that get exposed to the guests 💅✨

So like, this is the little struct that holds the receipts on which SMCCC hypercall services the guests are allowed to see. Main character energy for real 👑

🦋 SYNOPSIS 🦋

struct kvm_smccc_features {
    unsigned long std_bmap;
    unsigned long std_hyp_bmap;
    unsigned long vendor_hyp_bmap;
    unsigned long vendor_hyp_bmap_2;
 };

That's it, that's the whole vibe 🎀 four unsigned long bitmaps, no notes, no cap.

💖 MEMBERS 💖

• std_bmap — the bitmap of standard secure service calls, aka the standard secure service call bit squad 🌈
• std_hyp_bmap — the bitmap of standard hypervisor service calls — same energy, hypervisor flavoured 🧚
• vendor_hyp_bmap — the bitmap of vendor specific hypervisor service calls, i.e. the ones where each vendor does their own iconic thing 👑

ngl, vendor_hyp_bmap_2 is sitting right there in the struct too — the manpage just doesn't give it its own little description moment, so I'm not gonna make one up. Fr fr, only reporting what's on the page 🙈

⭐ SEE ALSO ⭐

• Kernel file ./arch/arm64/include/asm/kvm_host.h — go read it, iykyk 📖💜

That's the whole page, bestie, ate and left no crumbs 🍓 This one lives in ./arch/arm64/include/asm and the date on it is October 2026 — yes, October 2026, we're being soooo ahead of schedule 💀✨ mwah, drink some water before you go poke at KVM 🫶💖