vgic_lazy_init(9)

🌸 vgic_lazy_init(9) — from the Kernel API Manual 💅

okay so bestie, buckle up, because this one is a tiny little page from the Kernel API Manual and it's literally just vibes about when you're allowed to be lazy 🦋

---

✨ NAME ✨

vgic_lazy_init — the way that lazy init is only allowed if the GIC exposed to the guest is a GICv2. That's the whole vibe check, no cap 🎀

And like, a GICv3? Nope. A GICv3 must be explicitly initialized by userspace using the KVM_DEV_ARM_VGIC_GRP_CTRL KVM_DEVICE group. Not me explaining the rules but here we are 🙈

---

⭐ SYNOPSIS ⭐

int vgic_lazy_init (struct kvm *kvm );

like, that's it, that's the whole signature, iconic 👑

---

💖 ARGUMENTS 💖

• kvm — a kvm struct pointer. yes bestie, a pointer, to a kvm struct, we love a simple queen 🌸

---

🌈 SEE ALSO 🌈

fr fr go read these, they're all in the kernel file ./arch/arm64/kvm/vgic/vgic-init.c and they're lowkey the whole squad 🫶

• kvm_vgic_early_init(9)
• kvm_vgic_create(9)
• kvm_vgic_dist_init(9)
• kvm_vgic_vcpu_init(9)
• kvm_vgic_map_resources(9)
• kvm_vgic_init_cpu_hardware(9)
• kvm_vgic_hyp_init(9)

---

ok and like a lil PSA before you go: if the guest's GIC is a GICv3, lazy init is not it. userspace has to step up and do it explicitly with KVM_DEV_ARM_VGIC_GRP_CTRL in the KVM_DEVICE group. no shortcuts, periodt 💀

---

and that's the page!! 🧚 this little cutie lives in ./arch/arm64/kvm/vgic, dated October 2026, mwah 💜 slay, go init some virtual interrupts responsibly ✨🎀