vgic_v3_alloc_redist_region(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’œ vgic_v3_alloc_redist_region(9) β€” from the Kernel API Manual, bestie πŸŽ€

okay so picture this: you're deep in the vgic_v3_alloc_redist_region section of the Kernel API Manual and you're like "what does this even do" β€” don't worry, I got you. This is the page for vgic_v3_alloc_redist_region, and yes it's giving "arm64 KVM internals main character energy" ✨


🌸 NAME 🌸

vgic_v3_alloc_redist_region β€” literally just Allocate a new redistributor region. That's it. That's the whole vibe. πŸ’…


✨ SYNOPSIS ✨

int vgic_v3_alloc_redist_region (struct kvm *kvm , uint32_t index ,
gpa_t base , uint32_t count );

look at her. four arguments, returns an int, no cap. πŸ”₯


πŸ¦‹ ARGUMENTS πŸ¦‹

  • kvm β€” the kvm handle, your main character pointer 🫢
  • index β€” the redist region index (she has a position, as she should πŸ‘‘)
  • base β€” base of the new rdist region, where she lives 🏠
  • count β€” number of redistributors the region is made of. and this is the spicy bit: 0 means the old style single region, whose size is induced from the number of vcpus 🫠 iykyk

πŸ’– DESCRIPTION πŸ’–

so before she inserts the rdist region into the list, she does various checks β€” like a vibe check but for kernel data structures 😌 Those tests depend on whether the size of the rdist region is known (ie. count != 0). And the list? It's sorted by rdist region index. sorted bestie. always sorted. 🌈

Returns 0 on success, < 0 otherwise. so like... zero means slay, negative means 😭

πŸ‘‘ SEE ALSO πŸ‘‘

the whole friend group fr fr πŸ§šπŸ’œ


πŸŽ€ cute lil sign-off: this page came from ./arch/arm64/kvm/vgic, in the October 2026 era of the Kernel API Manual β€” periodt. πŸ’…βœ¨
πŸ“¦ where this page comes from