/linux/Documentation/firmware-guide/acpi/ |
H A D | method-tracing.rst | 85 …27] exdebug-0398 ex_trace_point : Method Begin [0xf58394d8:\_SB.PCI0.LPCB.ECOK] execution. 86 [ 0.186630] exdebug-0398 ex_trace_point : Opcode Begin [0xf5905c88:If] execution. 87 [ 0.186820] exdebug-0398 ex_trace_point : Opcode Begin [0xf5905cc0:LEqual] execution. 88 … 0.187010] exdebug-0398 ex_trace_point : Opcode Begin [0xf5905a20:-NamePath-] execution. 89 …[ 0.187214] exdebug-0398 ex_trace_point : Opcode End [0xf5905a20:-NamePath-] execution. 90 [ 0.187407] exdebug-0398 ex_trace_point : Opcode Begin [0xf5905f60:One] execution. 91 [ 0.187594] exdebug-0398 ex_trace_point : Opcode End [0xf5905f60:One] execution. 92 [ 0.187789] exdebug-0398 ex_trace_point : Opcode End [0xf5905cc0:LEqual] execution. 93 [ 0.187980] exdebug-0398 ex_trace_point : Opcode Begin [0xf5905cc0:Return] execution. 94 [ 0.188146] exdebug-0398 ex_trace_point : Opcode Begin [0xf5905f60:One] execution. [all …]
|
/linux/tools/perf/pmu-events/arch/x86/silvermont/ |
H A D | pipeline.json | 8 …execution path is known. All branches utilize the branch prediction unit (BPU) for prediction. Thi… 17 …execution path is known. All branches utilize the branch prediction unit (BPU) for prediction. Thi… 27 …execution path is known. All branches utilize the branch prediction unit (BPU) for prediction. Thi… 37 …execution path is known. All branches utilize the branch prediction unit (BPU) for prediction. Thi… 47 …execution path is known. All branches utilize the branch prediction unit (BPU) for prediction. Thi… 57 …execution path is known. All branches utilize the branch prediction unit (BPU) for prediction. Thi… 67 …execution path is known. All branches utilize the branch prediction unit (BPU) for prediction. Thi… 77 …execution path is known. All branches utilize the branch prediction unit (BPU) for prediction. Thi… 87 …execution path is known. All branches utilize the branch prediction unit (BPU) for prediction. Thi… 97 …execution path is known. All branches utilize the branch prediction unit (BPU) for prediction. Thi… [all …]
|
/linux/tools/perf/pmu-events/arch/x86/haswell/ |
H A D | memory.json | 3 "BriefDescription": "Number of times an HLE execution aborted due to any reasons (multiple categories may count as one).", 12 "BriefDescription": "Number of times an HLE execution aborted due to various memory events (e.g., read/write capacity and conflicts).", 20 "BriefDescription": "Number of times an HLE execution aborted due to uncommon conditions.", 28 "BriefDescription": "Number of times an HLE execution aborted due to HLE-unfriendly instructions.", 36 "BriefDescription": "Number of times an HLE execution aborted due to incompatible memory type.", 45 "BriefDescription": "Number of times an HLE execution aborted due to none of the previous 4 categories (e.g. interrupts)", 49 "PublicDescription": "Number of times an HLE execution aborted due to none of the previous 4 categories (e.g. interrupts).", 54 "BriefDescription": "Number of times an HLE execution successfully committed.", 62 "BriefDescription": "Number of times an HLE execution started.", 411 "BriefDescription": "Number of times an RTM execution aborte [all...] |
/linux/tools/testing/selftests/exec/ |
H A D | check-exec-tests.sh | 30 echo "ERROR: Wrong expectation for direct file execution: ${ret}" 34 echo "ERROR: Wrong output for direct file execution: ${out}" 50 echo "ERROR: Wrong expectation for indirect file execution: ${ret}" 54 echo "ERROR: Wrong output for indirect file execution: ${out}" 70 echo "ERROR: Wrong expectation for stdin regular file execution: ${ret}" 74 echo "ERROR: Wrong output for stdin regular file execution: ${out}" 89 echo "ERROR: Wrong expectation for stdin pipe execution: ${ret}" 104 echo "ERROR: Wrong expectation for arbitrary argument execution: ${ret}" 108 echo "ERROR: Wrong output for arbitrary argument execution: ${out}" 135 # We get 126 because of direct execution by Bash. [all …]
|
/linux/drivers/crypto/intel/qat/qat_common/ |
H A D | adf_gen4_tl.c | 84 /* Slice execution counters. */ 86 /* Compression slice execution count. */ 88 /* Translator slice execution count. */ 90 /* Decompression slice execution count. */ 92 /* PKE execution count. */ 94 /* Wireless Authentication slice execution count. */ 96 /* Wireless Cipher slice execution count. */ 98 /* UCS slice execution count. */ 100 /* Cipher slice execution count. */ 102 /* Authentication slice execution count. */
|
/linux/Documentation/userspace-api/ |
H A D | check_exec.rst | 11 consistent execution security policy handled by the kernel. See the 15 security risk of running malicious scripts with respect to the execution 23 Script interpreters or dynamic linkers built for tailored execution environments 37 check on a regular file and returns 0 if execution of this file would be 49 execution environment to ensure that direct file execution (e.g. 50 ``./script.sh``) and indirect file execution (e.g. ``sh script.sh``) lead to 56 are allowed for execution to avoid trivial bypass (e.g. using ``LD_PRELOAD``). 57 For such secure execution environment to make sense, only trusted code should 87 arbitrary code execution e.g., by enforcing a write xor execute policy. 96 should always deny such execution if ``SECBIT_EXEC_DENY_INTERACTIVE`` is set.
|
/linux/tools/perf/pmu-events/arch/x86/haswellx/ |
H A D | memory.json | 3 …"BriefDescription": "Number of times an HLE execution aborted due to any reasons (multiple categor… 12 …"BriefDescription": "Number of times an HLE execution aborted due to various memory events (e.g., … 20 "BriefDescription": "Number of times an HLE execution aborted due to uncommon conditions.", 28 …"BriefDescription": "Number of times an HLE execution aborted due to HLE-unfriendly instructions.", 36 … "BriefDescription": "Number of times an HLE execution aborted due to incompatible memory type.", 45 …"BriefDescription": "Number of times an HLE execution aborted due to none of the previous 4 catego… 49 …"PublicDescription": "Number of times an HLE execution aborted due to none of the previous 4 categ… 54 "BriefDescription": "Number of times an HLE execution successfully committed.", 62 "BriefDescription": "Number of times an HLE execution started.", 481 …"BriefDescription": "Number of times an RTM execution aborted due to any reasons (multiple categor… [all …]
|
/linux/drivers/gpu/drm/xe/ |
H A D | xe_hw_engine_group_types.h | 14 * enum xe_hw_engine_group_execution_mode - possible execution modes of a hw 17 * @EXEC_MODE_LR: execution in long-running mode 18 * @EXEC_MODE_DMA_FENCE: execution in dma fence mode 43 * mutual exclusion between execution only in faulting LR mode and 44 * execution only in DMA_FENCE mode 47 /** @cur_mode: current execution mode of this hw engine group */
|
/linux/Documentation/core-api/ |
H A D | workqueue.rst | 13 There are many cases where an asynchronous process execution context 17 When such an asynchronous execution context is needed, a work item 19 independent thread serves as the asynchronous execution context. The 42 worker pool. An MT wq could provide only one execution context per CPU 44 those very limited execution contexts leading to various problems 45 including proneness to deadlocks around the single execution context. 71 In order to ease the asynchronous execution of functions a new 97 concurrent execution context, there's no need to worry about concurrency. 99 the BH execution context. A BH workqueue can be considered a convenience 118 (how many execution contexts are active) is an important issue. cmwq [all …]
|
/linux/tools/perf/pmu-events/arch/x86/tigerlake/ |
H A D | memory.json | 3 "BriefDescription": "Execution stalls while L3 cache miss demand load is outstanding.", 126 "BriefDescription": "Number of times an RTM execution aborted.", 135 "BriefDescription": "Number of times an RTM execution aborted due to none of the previous 3 categories (e.g. interrupt)", 139 "PublicDescription": "Counts the number of times an RTM execution aborted due to none of the previous 3 categories (e.g. interrupt).", 144 "BriefDescription": "Number of times an RTM execution aborted due to various memory events (e.g. read/write capacity and conflicts)", 148 "PublicDescription": "Counts the number of times an RTM execution aborted due to various memory events (e.g. read/write capacity and conflicts).", 153 "BriefDescription": "Number of times an RTM execution aborted due to incompatible memory type", 157 "PublicDescription": "Counts the number of times an RTM execution aborted due to incompatible memory type.", 162 "BriefDescription": "Number of times an RTM execution aborted due to HLE-unfriendly instructions", 166 "PublicDescription": "Counts the number of times an RTM execution aborte [all...] |
/linux/Documentation/bpf/ |
H A D | bpf_prog_run.rst | 49 returned to userspace. A separate mode for live execution of XDP programs is 57 be processed by the kernel after the execution of the XDP program as if they 62 The live packet mode is optimised for high performance execution of the supplied 67 - When executing an XDP program in live frame mode, the result of the execution 73 specifically, only fatal errors in setup or during execution (like memory 74 allocation errors) will halt execution and return an error. If an error occurs 76 execution will continue with the next repetition; these errors can be detected 86 because the program execution is not happening in driver context, an 91 - When running the program with multiple repetitions, the execution will happen
|
/linux/Documentation/admin-guide/hw-vuln/ |
H A D | spectre.rst | 7 and speculative execution on modern CPUs to read memory, possibly 8 bypassing access controls. Speculative execution side channel exploits 16 Speculative execution side channel methods affect a wide range of modern 18 use branch prediction and speculative execution. 56 influence the speculative execution paths, and then use the side effects 57 of the speculative execution in the CPUs' caches and buffers to infer 58 privileged data touched during the speculative execution. 60 Spectre variant 1 attacks take advantage of speculative execution of 62 execution of indirect branches to leak privileged memory. 70 of speculative execution that bypasses conditional branch instructions [all …]
|
/linux/Documentation/arch/arm64/ |
H A D | legacy_instructions.rst | 9 the instruction execution in hardware. 12 (/proc/sys/abi). The following explains the different execution 29 * Hardware Execution 33 enabling/disabling of hardware support for the execution of these 34 instructions. Using hardware execution generally provides better
|
/linux/tools/perf/pmu-events/arch/x86/broadwellde/ |
H A D | memory.json | 13 "BriefDescription": "Number of times an HLE execution aborted due to various memory events (e.g., read/write capacity and conflicts).", 22 "BriefDescription": "Number of times an HLE execution aborted due to uncommon conditions", 31 "BriefDescription": "Number of times an HLE execution aborted due to HLE-unfriendly instructions", 40 "BriefDescription": "Number of times an HLE execution aborted due to incompatible memory type", 49 "BriefDescription": "Number of times an HLE execution aborted due to none of the previous 4 categories (e.g. interrupts)", 225 "BriefDescription": "Number of times an RTM execution aborted due to various memory events (e.g. read/write capacity and conflicts)", 234 "BriefDescription": "Number of times an RTM execution aborted due to various memory events (e.g., read/write capacity and conflicts).", 243 "BriefDescription": "Number of times an RTM execution aborted due to HLE-unfriendly instructions", 252 "BriefDescription": "Number of times an RTM execution aborted due to incompatible memory type", 261 "BriefDescription": "Number of times an RTM execution aborte [all...] |
/linux/tools/perf/pmu-events/arch/x86/skylakex/ |
H A D | memory.json | 12 "BriefDescription": "Execution stalls while L3 cache miss demand load is outstanding.", 21 …"BriefDescription": "Number of times an HLE execution aborted due to any reasons (multiple categor… 31 …"BriefDescription": "Number of times an HLE execution aborted due to unfriendly events (such as in… 39 …"BriefDescription": "Number of times an HLE execution aborted due to various memory events (e.g., … 47 … "BriefDescription": "Number of times an HLE execution aborted due to incompatible memory type", 51 … "PublicDescription": "Number of times an HLE execution aborted due to incompatible memory type.", 56 … "BriefDescription": "Number of times an HLE execution aborted due to hardware timer expiration.", 64 …"BriefDescription": "Number of times an HLE execution aborted due to HLE-unfriendly instructions a… 72 "BriefDescription": "Number of times an HLE execution successfully committed", 81 "BriefDescription": "Number of times an HLE execution started.", [all …]
|
/linux/tools/perf/pmu-events/arch/x86/skylake/ |
H A D | memory.json | 12 "BriefDescription": "Execution stalls while L3 cache miss demand load is outstanding.", 21 …"BriefDescription": "Number of times an HLE execution aborted due to any reasons (multiple categor… 31 …"BriefDescription": "Number of times an HLE execution aborted due to unfriendly events (such as in… 39 …"BriefDescription": "Number of times an HLE execution aborted due to various memory events (e.g., … 47 … "BriefDescription": "Number of times an HLE execution aborted due to incompatible memory type", 51 … "PublicDescription": "Number of times an HLE execution aborted due to incompatible memory type.", 56 … "BriefDescription": "Number of times an HLE execution aborted due to hardware timer expiration.", 64 …"BriefDescription": "Number of times an HLE execution aborted due to HLE-unfriendly instructions a… 72 "BriefDescription": "Number of times an HLE execution successfully committed", 81 "BriefDescription": "Number of times an HLE execution started.", [all …]
|
/linux/tools/perf/pmu-events/arch/x86/amdzen1/ |
H A D | floating-point.json | 6 …of operations (uOps) and dual-pipe uOps dispatched to each of the 4 FPU execution pipelines. This … 13 …of operations (uOps) and dual-pipe uOps dispatched to each of the 4 FPU execution pipelines. This … 20 …of operations (uOps) and dual-pipe uOps dispatched to each of the 4 FPU execution pipelines. This … 27 …of operations (uOps) and dual-pipe uOps dispatched to each of the 4 FPU execution pipelines. This … 34 …of operations (uOps) and dual-pipe uOps dispatched to each of the 4 FPU execution pipelines. This … 41 …of operations (uOps) and dual-pipe uOps dispatched to each of the 4 FPU execution pipelines. This … 48 …"PublicDescription": "The number of operations (uOps) dispatched to each of the 4 FPU execution pi… 55 …"PublicDescription": "The number of operations (uOps) dispatched to each of the 4 FPU execution pi… 62 …"PublicDescription": "The number of operations (uOps) dispatched to each of the 4 FPU execution pi… 69 …"PublicDescription": "The number of operations (uOps) dispatched to each of the 4 FPU execution pi…
|
/linux/drivers/tee/ |
H A D | Kconfig | 2 # Generic Trusted Execution Environment Configuration 4 tristate "Trusted Execution Environment support" 11 This implements a generic interface towards a Trusted Execution
|
/linux/include/linux/ |
H A D | psp-tee.h | 3 * AMD Trusted Execution Environment (TEE) interface 17 /* This file defines the Trusted Execution Environment (TEE) interface commands 45 * psp_tee_process_cmd() - Process command in Trusted Execution Environment 50 * @status: On success, holds the TEE command execution status
|
/linux/Documentation/ABI/testing/ |
H A D | debugfs-driver-qat_telemetry | 65 exec_cpr<N> execution count of Compression slice N 67 exec_xlt<N> execution count of Translator slice N 69 exec_dcpr<N> execution count of Decompression slice N 71 exec_pke<N> execution count of PKE N 73 exec_ucs<N> execution count of UCS slice N 76 exec_wat<N> execution count of Wireless Authentication 79 exec_wcp<N> execution count of Wireless Cipher slice N 81 exec_cph<N> execution count of Cipher slice N 83 exec_ath<N> execution count of Authentication slice N
|
/linux/Documentation/driver-api/nfc/ |
H A D | nfc-hci.rst | 28 HCI uses 2 execution contexts: 195 Execution Contexts 198 The execution contexts are the following: 211 Serializes execution of HCI commands. 213 Completes execution in case of response timeout. 236 Internally, execution is asynchronous. So all this API does is to enqueue the 253 waiting command execution. Response processing involves invoking the completion 282 Errors that occur synchronously with the execution of an NFC Core request are 283 simply returned as the execution result of the request. These are easy.
|
/linux/drivers/acpi/acpica/ |
H A D | extrace.c | 4 * Module Name: extrace - Support for interpreter execution tracing 120 * begin - TRUE if before execution 126 * DESCRIPTION: Internal interpreter execution trace. 139 "%s %s [0x%p:%s] execution.\n", in acpi_ex_trace_point() 144 "%s %s [0x%p] execution.\n", in acpi_ex_trace_point() 212 * DESCRIPTION: Start control method execution trace 269 * DESCRIPTION: Stop control method execution trace 325 * DESCRIPTION: Start opcode execution trace 353 * DESCRIPTION: Stop opcode execution trace
|
/linux/tools/perf/pmu-events/arch/x86/broadwellx/ |
H A D | memory.json | 13 "BriefDescription": "Number of times an HLE execution aborted due to various memory events (e.g., read/write capacity and conflicts).", 22 "BriefDescription": "Number of times an HLE execution aborted due to uncommon conditions", 31 "BriefDescription": "Number of times an HLE execution aborted due to HLE-unfriendly instructions", 40 "BriefDescription": "Number of times an HLE execution aborted due to incompatible memory type", 49 "BriefDescription": "Number of times an HLE execution aborted due to none of the previous 4 categories (e.g. interrupts)", 415 "BriefDescription": "Number of times an RTM execution aborted due to various memory events (e.g. read/write capacity and conflicts)", 424 "BriefDescription": "Number of times an RTM execution aborted due to various memory events (e.g., read/write capacity and conflicts).", 433 "BriefDescription": "Number of times an RTM execution aborted due to HLE-unfriendly instructions", 442 "BriefDescription": "Number of times an RTM execution aborted due to incompatible memory type", 451 "BriefDescription": "Number of times an RTM execution aborte [all...] |
/linux/Documentation/trace/ |
H A D | osnoise-tracer.rst | 25 the latency. The hwlat detects the NMI execution by observing 30 all the sources of *osnoise* during its execution. Using the same approach 151 the thread_noise, starting a irq_noise. When the IRQ ends its execution, 154 IRQ execution. This logic is valid for all sources of noise. 166 timer IRQ execution. The first event is not part of the noise because 172 before and after any interference execution. This justifies the dual 179 the osnoise: tracepoints serve to measure the execution time of
|
/linux/tools/perf/pmu-events/arch/s390/cf_z14/ |
H A D | extended.json | 91 …"PublicDescription": "A TEND instruction has completed in a constrained transactional-execution mo… 98 …Description": "A TEND instruction has completed in a non-constrained transactional-execution mode." 314 "BriefDescription": "BCD DFP Execution Slots", 315 …"PublicDescription": "Count of floating point execution slots used for finished Binary Coded Decim… 321 "BriefDescription": "VX BCD Execution Slots", 322 …"PublicDescription": "Count of floating point execution slots used for finished vector arithmetic … 343 …Description": "A transaction abort has occurred in a non-constrained transactional-execution mode." 350 …"PublicDescription": "A transaction abort has occurred in a constrained transactional-execution mo… 357 …"PublicDescription": "A transaction abort has occurred in a constrained transactional-execution mo…
|