It is at times necessary to prevent a guest from being able to sample certain events if multiple CPUs share resources such as a cache level. In this case, it would be interesting if the VMM could simply prevent certain events from being counted instead of hiding the PMU. Given that most events are not architected, there is no easy way to designate which events shouldn't be counted other than specifying the raw event number. Since I have no idea whether it is better to use an event whitelist or blacklist, the proposed API takes a cue from the x86 version and allows either allowing or denying counting of ranges of events. The event space being pretty large (16bits on ARMv8.1), the default policy is set by the first filter that gets installed (default deny if we first allow, default allow if we first deny). The filter state is global to the guest, despite the PMU being per CPU. I'm not sure whether it would be worth it making it CPU-private. As an example of what can be done in userspace, I have the corresponding kvmtool hack here[1]. * From v1: - Cleaned up handling of the cycle counter - Documented restrictions on SW_INC, CHAIN and CPU_CYCLES events [1] https://git.kernel.org/pub/scm/linux/kernel/git/maz/kvmtool.git/commit/?h=pmu-filter Marc Zyngier (2): KVM: arm64: Add PMU event filtering infrastructure KVM: arm64: Document PMU filtering API Documentation/virt/kvm/devices/vcpu.rst | 40 ++++++++++++ arch/arm64/include/asm/kvm_host.h | 6 ++ arch/arm64/include/uapi/asm/kvm.h | 16 +++++ virt/kvm/arm/arm.c | 2 + virt/kvm/arm/pmu.c | 84 ++++++++++++++++++++----- 5 files changed, 132 insertions(+), 16 deletions(-) -- 2.20.1
