1What:           /sys/bus/event_source/devices/hv_gpci/format
2Date:           September 2020
3Contact:        Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
4Description:    Read-only. Attribute group to describe the magic bits
5                that go into perf_event_attr.config for a particular pmu.
6                (See ABI/testing/sysfs-bus-event_source-devices-format).
7
8                Each attribute under this group defines a bit range of the
9                perf_event_attr.config. All supported attributes are listed
10                below::
11
12				counter_info_version  = "config:16-23"
13				length  = "config:24-31"
14				partition_id  = "config:32-63"
15				request = "config:0-31"
16				sibling_part_id = "config:32-63"
17				hw_chip_id = "config:32-63"
18				offset = "config:32-63"
19				phys_processor_idx = "config:32-63"
20				secondary_index = "config:0-15"
21				starting_index = "config:32-63"
22
23                For example::
24
25		  processor_core_utilization_instructions_completed = "request=0x94,
26					phys_processor_idx=?,counter_info_version=0x8,
27					length=8,offset=0x18"
28
29		In this event, '?' after phys_processor_idx specifies this value
30		this value will be provided by user while running this event.
31
32What:		/sys/bus/event_source/devices/hv_gpci/interface/collect_privileged
33Date:		February 2014
34Contact:	Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
35Description:
36		'0' if the hypervisor is configured to forbid access to event
37		counters being accumulated by other guests and to physical
38		domain event counters.
39
40		'1' if that access is allowed.
41
42What:		/sys/bus/event_source/devices/hv_gpci/interface/ga
43Date:		February 2014
44Contact:	Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
45Description:
46		0 or 1. Indicates whether we have access to "GA" events (listed
47		in arch/powerpc/perf/hv-gpci.h).
48
49What:		/sys/bus/event_source/devices/hv_gpci/interface/expanded
50Date:		February 2014
51Contact:	Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
52Description:
53		0 or 1. Indicates whether we have access to "EXPANDED" events (listed
54		in arch/powerpc/perf/hv-gpci.h).
55
56What:		/sys/bus/event_source/devices/hv_gpci/interface/lab
57Date:		February 2014
58Contact:	Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
59Description:
60		0 or 1. Indicates whether we have access to "LAB" events (listed
61		in arch/powerpc/perf/hv-gpci.h).
62
63What:		/sys/bus/event_source/devices/hv_gpci/interface/version
64Date:		February 2014
65Contact:	Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
66Description:
67		A number indicating the version of the gpci interface that the
68		hypervisor reports supporting.
69
70What:		/sys/bus/event_source/devices/hv_gpci/interface/kernel_version
71Date:		February 2014
72Contact:	Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
73Description:
74		A number indicating the latest version of the gpci interface
75		that the kernel is aware of.
76
77What:		/sys/devices/hv_gpci/cpumask
78Date:		October 2020
79Contact:	Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
80Description:	read only
81		This sysfs file exposes the cpumask which is designated to make
82		HCALLs to retrieve hv-gpci pmu event counter data.
83