Searched refs:fixed_counter_bitmap (Results 1 – 6 of 6) sorted by relevance
27 __u32 fixed_counter_bitmap; member726 f.fixed_counter_bitmap = ~GENMASK_ULL(nr_fixed_counters, 0); in test_filter_ioctl()752 .fixed_counter_bitmap = bitmap, in test_with_fixed_counter_filter()766 f.fixed_counter_bitmap = bitmap; in test_set_gp_and_fixed_event_filter()
477 test_bit(fixed_idx, (ulong *)&filter->fixed_counter_bitmap)) in is_fixed_event_allowed()480 !test_bit(fixed_idx, (ulong *)&filter->fixed_counter_bitmap)) in is_fixed_event_allowed()1120 filter->fixed_counter_bitmap = tmp.fixed_counter_bitmap; in kvm_vm_ioctl_set_pmu_event_filter()
564 __u32 fixed_counter_bitmap; member
1238 __u32 fixed_counter_bitmap; member
5194 __u32 fixed_counter_bitmap;5206 are controlled by the fixed_counter_bitmap.5270 counters (if any) by configuring the "action" and "fixed_counter_bitmap" fields.5279 KVM always consumes fixed_counter_bitmap, it's userspace's responsibility to5280 ensure fixed_counter_bitmap is set correctly, e.g. if userspace wants to define5284 and unit_mask values. "fixed_counter_bitmap" has higher priority than "events"