aboutsummaryrefslogtreecommitdiffstats
path: root/include/kvm
diff options
context:
space:
mode:
authorMarc Zyngier <maz@kernel.org>2020-02-12 11:31:02 +0000
committerMarc Zyngier <maz@kernel.org>2020-09-29 14:19:39 +0100
commitd7eec2360e389cc877a76c2b098f7b745007d2b2 (patch)
treedd02d8bbb5c295b5de4be83deb0a5e297187967c /include/kvm
parentKVM: arm64: Use event mask matching architecture revision (diff)
downloadlinux-dev-d7eec2360e389cc877a76c2b098f7b745007d2b2.tar.xz
linux-dev-d7eec2360e389cc877a76c2b098f7b745007d2b2.zip
KVM: arm64: Add PMU event filtering infrastructure
It can be desirable to expose a PMU to a guest, and yet not want the guest to be able to count some of the implemented events (because this would give information on shared resources, for example. For this, let's extend the PMUv3 device API, and offer a way to setup a bitmap of the allowed events (the default being no bitmap, and thus no filtering). Userspace can thus allow/deny ranges of event. The default policy depends on the "polarity" of the first filter setup (default deny if the filter allows events, and default allow if the filter denies events). This allows to setup exactly what is allowed for a given guest. Note that although the ioctl is per-vcpu, the map of allowed events is global to the VM (it can be setup from any vcpu until the vcpu PMU is initialized). Reviewed-by: Andrew Jones <drjones@redhat.com> Signed-off-by: Marc Zyngier <maz@kernel.org>
Diffstat (limited to 'include/kvm')
0 files changed, 0 insertions, 0 deletions