| /linux/tools/perf/Documentation/ |
| H A D | perf-arm-spe.txt | 16 The SPE (Statistical Profiling Extension) feature provides accurate attribution of latencies and 32 This is chosen from a sample population, for SPE this is an IMPLEMENTATION DEFINED choice of all 34 architecture provides a mechanism for the SPE driver to infer the minimum interval at which it shou… 64 Up until this point no decoding of the SPE data was done by either the kernel or Perf. Only when the 67 recording. These samples are the same as if normal sampling was done by Perf without using SPE, 69 just the instruction pointer, but an SPE sample can have data addresses and latency attributes. 84 However, SPE does not provide any call-graph information, and relies on statistical methods. 123 The SPE interrupt must also be described by the firmware. If the module is loaded and KPTI is 124 disabled (or isn't required to be disabled) but the SPE PMU still doesn't show in 125 /sys/bus/event_source/devices/, then it's possible that the SPE interrupt isn't described by [all …]
|
| H A D | perf-c2c.txt | 25 limitations, perf c2c is not supported on Zen3 cpus). On Arm64 it uses SPE to 28 statistical nature of Arm SPE sampling, not every memory operation will be 195 …| SPE |---------------+-----------------+------------------------------------------------------…
|
| H A D | perf-mem.txt | 26 On Arm64 this uses SPE to sample load and store operations, therefore hardware 28 Due to the statistical nature of SPE sampling, not every memory operation will
|
| H A D | perf-record.txt | 559 PERF_RECORD_SWITCH_CPU_WIDE. In some cases (e.g. Intel PT, CoreSight or Arm SPE)
|
| /linux/arch/powerpc/crypto/ |
| H A D | Kconfig | 6 tristate "Ciphers: AES, modes: ECB/CBC/CTR/XTS (SPE)" 7 depends on SPE 14 - SPE (Signal Processing Engine) extensions 16 SPE is available for:
|
| /linux/sound/soc/sdca/ |
| H A D | sdca_functions.c | 345 case SDCA_CTL_TYPE_S(SPE, PRIVATE): in find_sdca_control_label() 347 case SDCA_CTL_TYPE_S(SPE, PRIVACY_POLICY): in find_sdca_control_label() 349 case SDCA_CTL_TYPE_S(SPE, PRIVACY_LOCKSTATE): in find_sdca_control_label() 351 case SDCA_CTL_TYPE_S(SPE, PRIVACY_OWNER): in find_sdca_control_label() 353 case SDCA_CTL_TYPE_S(SPE, AUTHTX_CURRENTOWNER): in find_sdca_control_label() 355 case SDCA_CTL_TYPE_S(SPE, AUTHTX_MESSAGEOFFSET): in find_sdca_control_label() 357 case SDCA_CTL_TYPE_S(SPE, AUTHTX_MESSAGELENGTH): in find_sdca_control_label() 359 case SDCA_CTL_TYPE_S(SPE, AUTHRX_CURRENTOWNER): in find_sdca_control_label() 361 case SDCA_CTL_TYPE_S(SPE, AUTHRX_MESSAGEOFFSET): in find_sdca_control_label() 363 case SDCA_CTL_TYPE_S(SPE, AUTHRX_MESSAGELENGTH): in find_sdca_control_label() [all …]
|
| /linux/arch/powerpc/boot/dts/fsl/ |
| H A D | e500v2_power_isa.dtsi | 47 power-isa-sp.fd; // SPE.Embedded Float Scalar Double 48 power-isa-sp.fs; // SPE.Embedded Float Scalar Single 49 power-isa-sp.fv; // SPE.Embedded Float Vector
|
| H A D | e500v1_power_isa.dtsi | 47 power-isa-sp.fs; // SPE.Embedded Float Scalar Single 48 power-isa-sp.fv; // SPE.Embedded Float Vector
|
| /linux/drivers/gpib/include/ |
| H A D | gpib_cmd.h | 26 SPE = 0x18, /* serial poll enable */ enumerator
|
| /linux/arch/powerpc/platforms/ |
| H A D | Kconfig.cputype | 393 config SPE config 394 bool "SPE Support" 399 Extensions (SPE) to the PowerPC processor. The kernel currently 400 supports saving and restoring SPE registers, and turning on the 401 'spe enable' bit so user processes can execute SPE instructions. 404 SPE (e500, otherwise known as 85xx series), but does not have any
|
| /linux/lib/crypto/ |
| H A D | Kconfig | 19 default y if PPC && (SPE || (PPC64 && VSX)) 219 default y if PPC && SPE
|
| /linux/Documentation/networking/pse-pd/ |
| H A D | pse-pi.rst | 27 Single Pair Ethernet (SPE) represents a different approach to Ethernet 31 two pairs of wires, SPE operates on a simpler model due to its single-pair 34 Ethernet, are not applicable to SPE.
|
| /linux/Documentation/networking/diagnostic/ |
| H A D | twisted_pair_layer1_diagnostics.rst | 29 environments, including **Single-Pair Ethernet (SPE)** and **Multi-Pair 139 For both **Single-Pair Ethernet (SPE)** and **Multi-Pair Ethernet (MPE)** 140 devices, you will use this step to gather key details about the link. **SPE** 147 - **Example Output for SPE Interface (Non-autonegotiation)**: 336 The following are the typical outputs for **Single-Pair Ethernet (SPE)** and 339 - **For Single-Pair Ethernet (SPE)**: 340 - **Expected Output (SPE)**:
|
| /linux/Documentation/trace/coresight/ |
| H A D | coresight-perf.rst | 121 Check Arm SPE trace data recording and synthesized samples
|
| /linux/Documentation/arch/arm64/ |
| H A D | booting.rst | 469 For CPUs with SPE data source filtering (FEAT_SPE_FDS):
|
| /linux/drivers/gpib/common/ |
| H A D | gpib_os.c | 329 cmd_string[i++] = SPE; // serial poll enable in setup_serial_poll()
|
| /linux/arch/arm64/boot/dts/nvidia/ |
| H A D | tegra194.dtsi | 1563 * Shared interrupt 0 is routed only to AON/SPE, so
|
| H A D | tegra234.dtsi | 3910 * Shared interrupt 0 is routed only to AON/SPE, so
|
| /linux/arch/arm64/ |
| H A D | Kconfig | 2100 kernel memory such as SPE.
|
| /linux/Documentation/admin-guide/ |
| H A D | kernel-parameters.txt | 5454 Altivec, VSX and SPE outside of regions specifically
|