kvm_pmu_handle_pmcr(9)
π kvm_pmu_handle_pmcr(9) β like, the whole vibe check on this one
okay bestie, so this page lives in the Kernel API Manual, and the star of the show is kvm_pmu_handle_pmcr. Let's get into it β¨
πΈ NAME πΈ
kvm_pmu_handle_pmcr β handle PMCR register π
That's it, that's the whole job description. She handles the PMCR register. Iconic, lowkey.
π¦ SYNOPSIS π¦
void kvm_pmu_handle_pmcr (struct kvm_vcpu *vcpu , u64 val );
Note the return type: void. She does not return anything, she just does. Main character energy fr fr π
β¨ ARGUMENTS β¨
vcpuβ The vcpu pointer π«Ά this is the virtual CPU she's working her magic on.valβ the value guest writes to PMCR register. yes, the guest hands over this number and she deals with it, no cap.
both of these are needed, don't come for me with "can I skip one" β no. π₯°
π SEE ALSO π
the source lives right here in the kernel file ./arch/arm64/kvm/pmu-emul.c β that's the address, bestie, write it down π§
and now the whole friend group, all of them (9) section, in the exact order the manpage gives them, because I would never:
kvm_pmc_is_64bit(9)kvm_pmu_get_counter_value(9)kvm_pmu_set_counter_value(9)kvm_pmu_set_counter_value_user(9)kvm_pmu_release_perf_event(9)kvm_pmu_stop_counter(9)kvm_pmu_vcpu_init(9)kvm_pmu_vcpu_destroy(9)kvm_pmu_flush_hwstate(9)kvm_pmu_sync_hwstate(9)kvm_pmu_software_increment(9)kvm_pmu_create_perf_event(9)kvm_pmu_set_counter_event_type(9)kvm_arm_pmu_get_max_counters(9)kvm_arm_set_default_pmu(9)kvm_vcpu_read_pmcr(9)
sixteen of them, count 'em, I did π every single one is right there, exactly as written, don't @ me.
and that's the page!! π
cute little sign-off: this one's tagged with the source path ./arch/arm64/kvm and dated October 2026 β so yeah, she's got a timestamp and she's proud of it. bye bestie, go handle ya PMCR ππ¦π
π¦ 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