kvm_get_running_vcpus(9)
π kvm_get_running_vcpus(9) β from the Kernel API Manual, bestie
okay so picture this: you're deep in KVM land, and you need to know which vcpu is currently running on each CPU. That's literally the whole vibe of kvm_get_running_vcpus β it hands you the per-CPU array of the vcpus that are running right now. Not a copy, not a snapshot, the actual per-CPU array. Iconic.
β¨ NAME β¨
kvm_get_running_vcpus β get the per-CPU array of currently running vcpus. That's it, that's the whole job. π
πΈ SYNOPSIS πΈ
struct kvm_vcpu * __percpu * kvm_get_running_vcpus (void );
Look at that return type ngl β struct kvm_vcpu * __percpu *. It's giving pointer-to-per-CPU-pointer-to-vcpu realness. Read it slowly, it slays once you do. π
π¦ ARGUMENTS π¦
voidβ no arguments. Zero. None. She takes nothing and gives you the array. A low-maintenance icon. β¨
π₯ SEE ALSO π₯
- Kernel file
./virt/kvm/kvm_main.c kvm_get_dirty_log(9)kvm_get_dirty_log_protect(9)kvm_vm_ioctl_get_dirty_log(9)kvm_clear_dirty_log_protect(9)kvm_get_running_vcpu(9)β the singular bestie to this plural queen, go read that one too π«Ά
π the cute sign-off π
That's the whole page, bestie β short, sweet, and living in ./virt/kvm, dated October 2026, part of the Kernel API Manual fam. Go get your vcpus π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms