0001 What: /sys/devices/cpu/events/
0002 /sys/devices/cpu/events/branch-misses
0003 /sys/devices/cpu/events/cache-references
0004 /sys/devices/cpu/events/cache-misses
0005 /sys/devices/cpu/events/stalled-cycles-frontend
0006 /sys/devices/cpu/events/branch-instructions
0007 /sys/devices/cpu/events/stalled-cycles-backend
0008 /sys/devices/cpu/events/instructions
0009 /sys/devices/cpu/events/cpu-cycles
0010
0011 Date: 2013/01/08
0012
0013 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
0014
0015 Description: Generic performance monitoring events
0016
0017 A collection of performance monitoring events that may be
0018 supported by many/most CPUs. These events can be monitored
0019 using the 'perf(1)' tool.
0020
0021 The contents of each file would look like:
0022
0023 event=0xNNNN
0024
0025 where 'N' is a hex digit and the number '0xNNNN' shows the
0026 "raw code" for the perf event identified by the file's
0027 "basename".
0028
0029
0030 What: /sys/bus/event_source/devices/<pmu>/events/<event>
0031 Date: 2014/02/24
0032 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
0033 Description: Per-pmu performance monitoring events specific to the running system
0034
0035 Each file (except for some of those with a '.' in them, '.unit'
0036 and '.scale') in the 'events' directory describes a single
0037 performance monitoring event supported by the <pmu>. The name
0038 of the file is the name of the event.
0039
0040 File contents:
0041
0042 <term>[=<value>][,<term>[=<value>]]...
0043
0044 Where <term> is one of the terms listed under
0045 /sys/bus/event_source/devices/<pmu>/format/ and <value> is
0046 a number is base-16 format with a '0x' prefix (lowercase only).
0047 If a <term> is specified alone (without an assigned value), it
0048 is implied that 0x1 is assigned to that <term>.
0049
0050 Examples (each of these lines would be in a seperate file):
0051
0052 event=0x2abc
0053 event=0x423,inv,cmask=0x3
0054 domain=0x1,offset=0x8,starting_index=0xffff
0055 domain=0x1,offset=0x8,core=?
0056
0057 Each of the assignments indicates a value to be assigned to a
0058 particular set of bits (as defined by the format file
0059 corresponding to the <term>) in the perf_event structure passed
0060 to the perf_open syscall.
0061
0062 In the case of the last example, a value replacing "?" would
0063 need to be provided by the user selecting the particular event.
0064 This is referred to as "event parameterization". Event
0065 parameters have the format 'param=?'.
0066
0067 What: /sys/bus/event_source/devices/<pmu>/events/<event>.unit
0068 Date: 2014/02/24
0069 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
0070 Description: Perf event units
0071
0072 A string specifying the English plural numerical unit that <event>
0073 (once multiplied by <event>.scale) represents.
0074
0075 Example:
0076
0077 Joules
0078
0079 What: /sys/bus/event_source/devices/<pmu>/events/<event>.scale
0080 Date: 2014/02/24
0081 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
0082 Description: Perf event scaling factors
0083
0084 A string representing a floating point value expressed in
0085 scientific notation to be multiplied by the event count
0086 recieved from the kernel to match the unit specified in the
0087 <event>.unit file.
0088
0089 Example:
0090
0091 2.3283064365386962890625e-10
0092
0093 This is provided to avoid performing floating point arithmetic
0094 in the kernel.
