2015-07-06 19:23:53 +08:00
|
|
|
#
|
|
|
|
|
# Performance Monitor Drivers
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
menu "Performance monitor support"
|
2017-06-13 20:45:51 +08:00
|
|
|
depends on PERF_EVENTS
|
2015-07-06 19:23:53 +08:00
|
|
|
|
2018-02-16 02:51:42 +08:00
|
|
|
config ARM_CCI_PMU
|
2018-05-14 21:34:53 +08:00
|
|
|
tristate "ARM CCI PMU driver"
|
|
|
|
|
depends on (ARM && CPU_V7) || ARM64
|
2018-02-16 02:51:42 +08:00
|
|
|
select ARM_CCI
|
2018-05-14 21:34:53 +08:00
|
|
|
help
|
|
|
|
|
Support for PMU events monitoring on the ARM CCI (Cache Coherent
|
|
|
|
|
Interconnect) family of products.
|
|
|
|
|
|
|
|
|
|
If compiled as a module, it will be called arm-cci.
|
2018-02-16 02:51:42 +08:00
|
|
|
|
|
|
|
|
config ARM_CCI400_PMU
|
2018-05-14 21:34:53 +08:00
|
|
|
bool "support CCI-400"
|
|
|
|
|
default y
|
|
|
|
|
depends on ARM_CCI_PMU
|
2018-02-16 02:51:42 +08:00
|
|
|
select ARM_CCI400_COMMON
|
|
|
|
|
help
|
2018-05-14 21:34:53 +08:00
|
|
|
CCI-400 provides 4 independent event counters counting events related
|
|
|
|
|
to the connected slave/master interfaces, plus a cycle counter.
|
2018-02-16 02:51:42 +08:00
|
|
|
|
|
|
|
|
config ARM_CCI5xx_PMU
|
2018-05-14 21:34:53 +08:00
|
|
|
bool "support CCI-500/CCI-550"
|
|
|
|
|
default y
|
|
|
|
|
depends on ARM_CCI_PMU
|
2018-02-16 02:51:42 +08:00
|
|
|
help
|
2018-05-14 21:34:53 +08:00
|
|
|
CCI-500/CCI-550 both provide 8 independent event counters, which can
|
|
|
|
|
count events pertaining to the slave/master interfaces as well as the
|
|
|
|
|
internal events to the CCI.
|
2018-02-16 02:51:42 +08:00
|
|
|
|
2018-02-16 02:51:41 +08:00
|
|
|
config ARM_CCN
|
|
|
|
|
tristate "ARM CCN driver support"
|
|
|
|
|
depends on ARM || ARM64
|
|
|
|
|
help
|
|
|
|
|
PMU (perf) driver supporting the ARM CCN (Cache Coherent Network)
|
|
|
|
|
interconnect.
|
|
|
|
|
|
2015-07-06 19:23:53 +08:00
|
|
|
config ARM_PMU
|
2017-06-13 20:45:51 +08:00
|
|
|
depends on ARM || ARM64
|
2015-07-06 19:23:53 +08:00
|
|
|
bool "ARM PMU framework"
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Say y if you want to use CPU performance monitors on ARM-based
|
|
|
|
|
systems.
|
|
|
|
|
|
2017-04-11 16:39:55 +08:00
|
|
|
config ARM_PMU_ACPI
|
|
|
|
|
depends on ARM_PMU && ACPI
|
|
|
|
|
def_bool y
|
|
|
|
|
|
2018-01-02 19:25:33 +08:00
|
|
|
config ARM_DSU_PMU
|
|
|
|
|
tristate "ARM DynamIQ Shared Unit (DSU) PMU"
|
|
|
|
|
depends on ARM64
|
|
|
|
|
help
|
|
|
|
|
Provides support for performance monitor unit in ARM DynamIQ Shared
|
|
|
|
|
Unit (DSU). The DSU integrates one or more cores with an L3 memory
|
|
|
|
|
system, control logic. The PMU allows counting various events related
|
|
|
|
|
to DSU.
|
|
|
|
|
|
2017-10-19 19:05:17 +08:00
|
|
|
config HISI_PMU
|
|
|
|
|
bool "HiSilicon SoC PMU"
|
|
|
|
|
depends on ARM64 && ACPI
|
|
|
|
|
help
|
|
|
|
|
Support for HiSilicon SoC uncore performance monitoring
|
|
|
|
|
unit (PMU), such as: L3C, HHA and DDRC.
|
|
|
|
|
|
2017-02-08 02:14:04 +08:00
|
|
|
config QCOM_L2_PMU
|
|
|
|
|
bool "Qualcomm Technologies L2-cache PMU"
|
2017-06-13 20:45:51 +08:00
|
|
|
depends on ARCH_QCOM && ARM64 && ACPI
|
2017-02-08 02:14:04 +08:00
|
|
|
help
|
|
|
|
|
Provides support for the L2 cache performance monitor unit (PMU)
|
|
|
|
|
in Qualcomm Technologies processors.
|
|
|
|
|
Adds the L2 cache PMU into the perf events subsystem for
|
|
|
|
|
monitoring L2 cache events.
|
|
|
|
|
|
2017-04-01 02:13:43 +08:00
|
|
|
config QCOM_L3_PMU
|
|
|
|
|
bool "Qualcomm Technologies L3-cache PMU"
|
2017-06-13 20:45:51 +08:00
|
|
|
depends on ARCH_QCOM && ARM64 && ACPI
|
2017-04-01 02:13:43 +08:00
|
|
|
select QCOM_IRQ_COMBINER
|
|
|
|
|
help
|
|
|
|
|
Provides support for the L3 cache performance monitor unit (PMU)
|
|
|
|
|
in Qualcomm Technologies processors.
|
|
|
|
|
Adds the L3 cache PMU into the perf events subsystem for
|
|
|
|
|
monitoring L3 cache events.
|
|
|
|
|
|
2018-12-06 19:51:31 +08:00
|
|
|
config THUNDERX2_PMU
|
|
|
|
|
tristate "Cavium ThunderX2 SoC PMU UNCORE"
|
|
|
|
|
depends on ARCH_THUNDER2 && ARM64 && ACPI && NUMA
|
|
|
|
|
default m
|
|
|
|
|
help
|
|
|
|
|
Provides support for ThunderX2 UNCORE events.
|
|
|
|
|
The SoC has PMU support in its L3 cache controller (L3C) and
|
|
|
|
|
in the DDR4 Memory Controller (DMC).
|
|
|
|
|
|
2016-07-16 01:38:04 +08:00
|
|
|
config XGENE_PMU
|
2017-06-13 20:45:51 +08:00
|
|
|
depends on ARCH_XGENE
|
2016-07-16 01:38:04 +08:00
|
|
|
bool "APM X-Gene SoC PMU"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Say y if you want to use APM X-Gene SoC performance monitors.
|
|
|
|
|
|
drivers/perf: Add support for ARMv8.2 Statistical Profiling Extension
The ARMv8.2 architecture introduces the optional Statistical Profiling
Extension (SPE).
SPE can be used to profile a population of operations in the CPU pipeline
after instruction decode. These are either architected instructions (i.e.
a dynamic instruction trace) or CPU-specific uops and the choice is fixed
statically in the hardware and advertised to userspace via caps/. Sampling
is controlled using a sampling interval, similar to a regular PMU counter,
but also with an optional random perturbation to avoid falling into patterns
where you continuously profile the same instruction in a hot loop.
After each operation is decoded, the interval counter is decremented. When
it hits zero, an operation is chosen for profiling and tracked within the
pipeline until it retires. Along the way, information such as TLB lookups,
cache misses, time spent to issue etc is captured in the form of a sample.
The sample is then filtered according to certain criteria (e.g. load
latency) that can be specified in the event config (described under
format/) and, if the sample satisfies the filter, it is written out to
memory as a record, otherwise it is discarded. Only one operation can
be sampled at a time.
The in-memory buffer is linear and virtually addressed, raising an
interrupt when it fills up. The PMU driver handles these interrupts to
give the appearance of a ring buffer, as expected by the AUX code.
The in-memory trace-like format is self-describing (though not parseable
in reverse) and written as a series of records, with each record
corresponding to a sample and consisting of a sequence of packets. These
packets are defined by the architecture, although some have CPU-specific
fields for recording information specific to the microarchitecture.
As a simple example, a record generated for a branch instruction may
consist of the following packets:
0 (Address) : Virtual PC of the branch instruction
1 (Type) : Conditional direct branch
2 (Counter) : Number of cycles taken from Dispatch to Issue
3 (Address) : Virtual branch target + condition flags
4 (Counter) : Number of cycles taken from Dispatch to Complete
5 (Events) : Mispredicted as not-taken
6 (END) : End of record
It is also possible to toggle properties such as timestamp packets in
each record.
This patch adds support for SPE in the form of a new perf driver.
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Reviewed-by: Mark Rutland <mark.rutland@arm.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
2016-09-22 18:36:32 +08:00
|
|
|
config ARM_SPE_PMU
|
|
|
|
|
tristate "Enable support for the ARMv8.2 Statistical Profiling Extension"
|
2018-05-22 23:54:04 +08:00
|
|
|
depends on ARM64
|
drivers/perf: Add support for ARMv8.2 Statistical Profiling Extension
The ARMv8.2 architecture introduces the optional Statistical Profiling
Extension (SPE).
SPE can be used to profile a population of operations in the CPU pipeline
after instruction decode. These are either architected instructions (i.e.
a dynamic instruction trace) or CPU-specific uops and the choice is fixed
statically in the hardware and advertised to userspace via caps/. Sampling
is controlled using a sampling interval, similar to a regular PMU counter,
but also with an optional random perturbation to avoid falling into patterns
where you continuously profile the same instruction in a hot loop.
After each operation is decoded, the interval counter is decremented. When
it hits zero, an operation is chosen for profiling and tracked within the
pipeline until it retires. Along the way, information such as TLB lookups,
cache misses, time spent to issue etc is captured in the form of a sample.
The sample is then filtered according to certain criteria (e.g. load
latency) that can be specified in the event config (described under
format/) and, if the sample satisfies the filter, it is written out to
memory as a record, otherwise it is discarded. Only one operation can
be sampled at a time.
The in-memory buffer is linear and virtually addressed, raising an
interrupt when it fills up. The PMU driver handles these interrupts to
give the appearance of a ring buffer, as expected by the AUX code.
The in-memory trace-like format is self-describing (though not parseable
in reverse) and written as a series of records, with each record
corresponding to a sample and consisting of a sequence of packets. These
packets are defined by the architecture, although some have CPU-specific
fields for recording information specific to the microarchitecture.
As a simple example, a record generated for a branch instruction may
consist of the following packets:
0 (Address) : Virtual PC of the branch instruction
1 (Type) : Conditional direct branch
2 (Counter) : Number of cycles taken from Dispatch to Issue
3 (Address) : Virtual branch target + condition flags
4 (Counter) : Number of cycles taken from Dispatch to Complete
5 (Events) : Mispredicted as not-taken
6 (END) : End of record
It is also possible to toggle properties such as timestamp packets in
each record.
This patch adds support for SPE in the form of a new perf driver.
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Reviewed-by: Mark Rutland <mark.rutland@arm.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
2016-09-22 18:36:32 +08:00
|
|
|
help
|
|
|
|
|
Enable perf support for the ARMv8.2 Statistical Profiling
|
|
|
|
|
Extension, which provides periodic sampling of operations in
|
|
|
|
|
the CPU pipeline and reports this via the perf AUX interface.
|
|
|
|
|
|
2015-07-06 19:23:53 +08:00
|
|
|
endmenu
|