KVM: x86: Add fixed counters to PMU filter
Updates KVM_CAP_PMU_EVENT_FILTER so it can also whitelist or blacklist fixed counters. Signed-off-by: Eric Hankland <ehankland@google.com> [No need to check padding fields for zero. - Paolo] Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
This commit is contained in:

committed by
Paolo Bonzini

parent
88dddc11a8
commit
30cd860432
@@ -4090,17 +4090,22 @@ Parameters: struct kvm_pmu_event_filter (in)
|
||||
Returns: 0 on success, -1 on error
|
||||
|
||||
struct kvm_pmu_event_filter {
|
||||
__u32 action;
|
||||
__u32 nevents;
|
||||
__u64 events[0];
|
||||
__u32 action;
|
||||
__u32 nevents;
|
||||
__u32 fixed_counter_bitmap;
|
||||
__u32 flags;
|
||||
__u32 pad[4];
|
||||
__u64 events[0];
|
||||
};
|
||||
|
||||
This ioctl restricts the set of PMU events that the guest can program.
|
||||
The argument holds a list of events which will be allowed or denied.
|
||||
The eventsel+umask of each event the guest attempts to program is compared
|
||||
against the events field to determine whether the guest should have access.
|
||||
This only affects general purpose counters; fixed purpose counters can
|
||||
be disabled by changing the perfmon CPUID leaf.
|
||||
The events field only controls general purpose counters; fixed purpose
|
||||
counters are controlled by the fixed_counter_bitmap.
|
||||
|
||||
No flags are defined yet, the field must be zero.
|
||||
|
||||
Valid values for 'action':
|
||||
#define KVM_PMU_EVENT_ALLOW 0
|
||||
|
Reference in New Issue
Block a user