Home
last modified time | relevance | path

Searched full:trbe (Results 1 – 18 of 18) sorted by relevance

/linux-6.12.1/drivers/hwtracing/coresight/
Dcoresight-trbe.c3 * This driver enables Trace Buffer Extension (TRBE) as a per-cpu coresight
23 #include "coresight-trbe.h"
30 * data which could not be decoded. TRBE doesn't support
63 /* The base programmed into the TRBE */
74 * TRBE erratum list
78 * to the affected CPUs inside the TRBE driver, we need to know if
80 * work arounds, TRBE driver needs to check multiple times during
83 * We keep a set of the affected errata in trbe_cpudata, per TRBE.
86 * TRBE erratum. We map the given cpucap into a TRBE internal number
118 * struct trbe_cpudata: TRBE instance specific data
[all …]
DKconfig192 tristate "Trace Buffer Extension (TRBE) driver"
195 This driver provides support for percpu Trace Buffer Extension (TRBE).
196 TRBE always needs to be used along with its corresponding percpu ETE
197 component. ETE generates trace data which is then captured with TRBE.
198 Unlike traditional sink devices, TRBE is a CPU feature accessible via
203 called coresight-trbe.
Dcoresight-trbe.h4 * Trace Buffer Extension (TRBE) driver in the coresight framework.
25 unsigned int trbe = cpuid_feature_extract_unsigned_field(aa64dfr0, in is_trbe_available() local
28 return trbe >= ID_AA64DFR0_EL1_TraceBuffer_IMP; in is_trbe_available()
DMakefile47 obj-$(CONFIG_CORESIGHT_TRBE) += coresight-trbe.o
/linux-6.12.1/Documentation/trace/coresight/
Dcoresight-trbe.rst4 Trace Buffer Extension (TRBE).
13 Trace Buffer Extension (TRBE) is a percpu hardware which captures in system
18 The TRBE is not compliant to CoreSight architecture specifications, but is
25 The TRBE devices appear on the existing coresight bus alongside the other
31 The ``trbe<N>`` named TRBEs are associated with a CPU.::
37 * ``align``: TRBE write pointer alignment
38 * ``flag``: TRBE updates memory with access and dirty flags
/linux-6.12.1/Documentation/ABI/testing/
Dsysfs-bus-coresight-devices-trbe1 What: /sys/bus/coresight/devices/trbe<cpu>/align
5 Description: (Read) Shows the TRBE write pointer alignment. This value
8 What: /sys/bus/coresight/devices/trbe<cpu>/flag
12 Description: (Read) Shows if TRBE updates in the memory are with access
/linux-6.12.1/Documentation/devicetree/bindings/arm/
Darm,trace-buffer-extension.yaml14 Arm Trace Buffer Extension (TRBE) is a per CPU component
22 const: trbe
31 TRBE is only supported on a subset of the CPUs, please consult
46 trbe {
Darm,embedded-trace-extension.yaml20 Arm Trace Buffer Extension (TRBE)). Since the ETE can be connected to
/linux-6.12.1/arch/arm64/
DKconfig841 bool "Cortex-A710/X2: 2119858: workaround TRBE overwriting trace data in FILL mode"
859 bool "Neoverse-N2: 2139208: workaround TRBE overwriting trace data in FILL mode"
913 bool "Neoverse-N2: 2253138: workaround TRBE writing to address out-of-range"
921 for TRBE. Under some conditions, the TRBE might generate a write to the next
922 virtually addressed page following the last page of the TRBE address space
926 page beyond the TRBLIMITR_EL1.LIMIT, within the space allowed for the TRBE.
931 bool "Cortex-A710/X2: 2224489: workaround TRBE writing to address out-of-range"
939 for TRBE. Under some conditions, the TRBE might generate a write to the next
940 virtually addressed page following the last page of the TRBE address space
944 page beyond the TRBLIMITR_EL1.LIMIT, within the space allowed for the TRBE.
[all …]
/linux-6.12.1/arch/arm64/kvm/hyp/nvhe/
Ddebug-sr.c58 /* Check if the TRBE is enabled */ in __debug_save_trace()
Dswitch.c309 * above disabling of SPE and TRBE. in __kvm_vcpu_run()
/linux-6.12.1/include/linux/perf/
Darm_pmu.h188 #define ARMV8_TRBE_PDEV_NAME "arm,trbe"
/linux-6.12.1/arch/arm64/kernel/
Dhyp-stub.S115 // Use EL2 translations for SPE & TRBE and disable access from EL1
Dcpu_errata.c674 * The erratum work around is handled within the TRBE
/linux-6.12.1/arch/arm64/include/asm/
Del2_setup.h93 cbnz x0, .Lskip_trace_\@ // If TRBE is available at EL2
Dkvm_host.h904 /* Save TRBE context if active */
/linux-6.12.1/arch/arm64/kvm/
Ddebug.c335 /* Check if we have TRBE implemented and available at the host */ in kvm_arch_vcpu_load_debug_state_flags()
/linux-6.12.1/drivers/perf/
Darm_pmu_acpi.c191 pr_warn("ACPI: TRBE: Unable to register device\n"); in arm_trbe_acpi_register_device()