Home
last modified time | relevance | path

Searched refs:fixed_counter_bitmap (Results 1 – 5 of 5) sorted by relevance

/linux/tools/testing/selftests/kvm/x86/
H A Dpmu_event_filter_test.c27 __u32 fixed_counter_bitmap; member
726 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()
/linux/arch/x86/include/uapi/asm/
H A Dkvm.h566 __u32 fixed_counter_bitmap; member
/linux/tools/arch/x86/include/uapi/asm/
H A Dkvm.h565 __u32 fixed_counter_bitmap; member
/linux/arch/x86/include/asm/
H A Dkvm_host.h1258 __u32 fixed_counter_bitmap; member
/linux/Documentation/virt/kvm/
H A Dapi.rst5193 __u32 fixed_counter_bitmap;
5205 are controlled by the fixed_counter_bitmap.
5269 counters (if any) by configuring the "action" and "fixed_counter_bitmap" fields.
5278 KVM always consumes fixed_counter_bitmap, it's userspace's responsibility to
5279 ensure fixed_counter_bitmap is set correctly, e.g. if userspace wants to define
5283 and unit_mask values. "fixed_counter_bitmap" has higher priority than "events"