kvm_vgic_map_resources(9)

💅 kvm_vgic_map_resources — a Kernel API Manual moment 🎀

okay bestie, so this one lives in the Kernel API Manual (section 9, kernel dev stuff, iykyk) and it's genuinely so important — it's literally the function that maps the MMIO regions. let's get into it 💖

---

✨ NAME ✨

kvm_vgic_map_resources — maps the MMIO regions, that's the whole vibe 🗺️

---

🌸 SYNOPSIS 🌸

int kvm_vgic_map_resources (struct kvm *kvm );

that's it. that's the signature. slay 💅

---

🦋 ARGUMENTS 🦋

• kvm — a kvm struct pointer. just the pointer. that's your whole input bestie 🫶

---

💜 DESCRIPTION 💜

so what does it actually do? it maps the MMIO regions — and which ones it maps depends on the VGIC model that's exposed to the guest. and the timing? it's called on the first VCPU run. not before. the first VCPU run. periodt ⏰

it also maps the virtual CPU interface into the VM. iconic behavior honestly 🧚

now the model-specific tea ☕:

• v2 — calls vgic_init if that hasn't already been done. no drama, it just handles it for you 💖
• v3 and derivatives — these ones are not forgiving: they return an error if the VGIC is not initialized. so like, do the init first, bestie. don't come to v3 unprepared 😭

fr fr if you're on v3, make sure the VGIC is initialized before this runs — otherwise it's error city and nobody wants that 💀

---

🌈 SEE ALSO 🌈

all the related reading, in the kernel file ./arch/arm64/kvm/vgic/vgic-init.c:

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

---

🎀 sign-off 🎀

this page came to you straight from ./arch/arm64/kvm/vgic, dated October 2026 — and that's the whole manual page, no cap. go map those resources, main character 👑💜