Searched full:execution (Results 1 – 25 of 1271) sorted by relevance
12345678910>>...51
| /linux-5.10/Documentation/firmware-guide/acpi/ |
| 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-5.10/Documentation/core-api/ |
| 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
110 (how many execution contexts are active) is an important issue. cmwq
122 workers on the CPU, the worker-pool doesn't start execution of a new
126 without losing execution bandwidth.
[all …]
|
| /linux-5.10/tools/perf/pmu-events/arch/x86/icelake/ |
| D | memory.json | 44 …"BriefDescription": "Number of times an HLE transactional execution aborted due to NoAllocatedElis…
55 …"BriefDescription": "Number of times an HLE transactional execution aborted due to XRELEASE lock n…
66 …"BriefDescription": "Number of times an HLE transactional execution aborted due to an unsupported …
99 …"BriefDescription": "Number of times an instruction execution caused the transactional nest count …
120 "BriefDescription": "Execution stalls while L3 cache miss demand load is outstanding.",
154 "BriefDescription": "Number of times an HLE execution started."
165 "BriefDescription": "Number of times an HLE execution successfully committed",
177 …"BriefDescription": "Number of times an HLE execution aborted due to any reasons (multiple categor…
181 …"PublicDescription": "Counts the number of times an HLE execution aborted due to various memory ev…
188 …"BriefDescription": "Number of times an HLE execution aborted due to various memory events (e.g., …
[all …]
|
| /linux-5.10/tools/perf/pmu-events/arch/x86/silvermont/ |
| D | pipeline.json | 4 …execution path is known. All branches utilize the branch prediction unit (BPU) for prediction. Thi…
14 …execution path is known. All branches utilize the branch prediction unit (BPU) for prediction. Thi…
24 …execution path is known. All branches utilize the branch prediction unit (BPU) for prediction. Thi…
34 …execution path is known. All branches utilize the branch prediction unit (BPU) for prediction. Thi…
44 …execution path is known. All branches utilize the branch prediction unit (BPU) for prediction. Thi…
54 …execution path is known. All branches utilize the branch prediction unit (BPU) for prediction. Thi…
64 …execution path is known. All branches utilize the branch prediction unit (BPU) for prediction. Thi…
74 …execution path is known. All branches utilize the branch prediction unit (BPU) for prediction. Thi…
84 …execution path is known. All branches utilize the branch prediction unit (BPU) for prediction. Thi…
259 …"PublicDescription": "This event counts the number of instructions that retire execution. For inst…
[all …]
|
| /linux-5.10/tools/perf/pmu-events/arch/x86/haswell/ |
| D | memory.json | 55 …"BriefDescription": "Number of times an HLE transactional execution aborted due to NoAllocatedElis…
64 …"BriefDescription": "Number of times an HLE transactional execution aborted due to XRELEASE lock n…
73 …"BriefDescription": "Number of times an HLE transactional execution aborted due to an unsupported …
91 …ay cause a transactional abort was executed. Since this is the count of execution, it may not alwa…
109 …"BriefDescription": "Counts the number of times an instruction execution caused the transactional …
146 "BriefDescription": "Number of times an HLE execution started.",
155 "BriefDescription": "Number of times an HLE execution successfully committed.",
165 …"BriefDescription": "Number of times an HLE execution aborted due to any reasons (multiple categor…
174 …"BriefDescription": "Number of times an HLE execution aborted due to various memory events (e.g., …
183 "BriefDescription": "Number of times an HLE execution aborted due to uncommon conditions.",
[all …]
|
| /linux-5.10/Documentation/arm64/ |
| 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-5.10/Documentation/admin-guide/hw-vuln/ |
| 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-5.10/tools/perf/pmu-events/arch/x86/haswellx/ |
| D | memory.json | 52 …"BriefDescription": "Number of times an HLE transactional execution aborted due to NoAllocatedElis…
61 …"BriefDescription": "Number of times an HLE transactional execution aborted due to XRELEASE lock n…
70 …"BriefDescription": "Number of times an HLE transactional execution aborted due to an unsupported …
88 …ay cause a transactional abort was executed. Since this is the count of execution, it may not alwa…
106 …"BriefDescription": "Counts the number of times an instruction execution caused the transactional …
143 "BriefDescription": "Number of times an HLE execution started.",
152 "BriefDescription": "Number of times an HLE execution successfully committed.",
161 …"BriefDescription": "Number of times an HLE execution aborted due to any reasons (multiple categor…
171 …"BriefDescription": "Number of times an HLE execution aborted due to various memory events (e.g., …
180 "BriefDescription": "Number of times an HLE execution aborted due to uncommon conditions.",
[all …]
|
| /linux-5.10/drivers/tee/ |
| 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-5.10/tools/perf/pmu-events/arch/x86/broadwellde/ |
| D | memory.json | 95 …ay cause a transactional abort was executed. Since this is the count of execution, it may not alwa…
114 …"BriefDescription": "Counts the number of times an instruction execution caused the transactional …
184 …"BriefDescription": "Number of times an HLE execution aborted due to various memory events (e.g., …
194 "BriefDescription": "Number of times an HLE execution aborted due to uncommon conditions",
204 … "BriefDescription": "Number of times an HLE execution aborted due to HLE-unfriendly instructions",
214 … "BriefDescription": "Number of times an HLE execution aborted due to incompatible memory type",
224 …"BriefDescription": "Number of times an HLE execution aborted due to none of the previous 4 catego…
265 …"BriefDescription": "Number of times an RTM execution aborted due to various memory events (e.g. r…
275 …"BriefDescription": "Number of times an RTM execution aborted due to various memory events (e.g., …
285 … "BriefDescription": "Number of times an RTM execution aborted due to HLE-unfriendly instructions",
[all …]
|
| /linux-5.10/tools/perf/pmu-events/arch/x86/amdzen1/ |
| 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-5.10/include/linux/ |
| 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-5.10/block/ |
| D | blk-exec.c | 34 * blk_execute_rq_nowait - insert a request into queue for execution
43 * for execution. Don't wait for completion.
69 * blk_execute_rq - insert a request into queue for execution
77 * for execution and wait for completion.
|
| /linux-5.10/drivers/acpi/acpica/ |
| 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()
161 * DESCRIPTION: Start control method execution trace
218 * DESCRIPTION: Stop control method execution trace
274 * DESCRIPTION: Start opcode execution trace
302 * DESCRIPTION: Stop opcode execution trace
|
| /linux-5.10/Documentation/driver-api/nfc/ |
| 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-5.10/tools/perf/pmu-events/arch/s390/cf_z14/ |
| D | extended.json | 91 …"PublicDescription": "A TEND instruction has completed in a constrained transactional-execution mo…
98 …cDescription": "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 …cDescription": "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…
|
| /linux-5.10/Documentation/devicetree/bindings/dma/ |
| D | qcom_bam_dma.txt | 14 - qcom,ee : indicates the active Execution Environment identifier (0-7) used in
17 remote proccessor i.e. execution environment.
20 - qcom,num-ees : optional, indicates supported number of Execution Environments
|
| /linux-5.10/Documentation/sparc/oradax/ |
| D | dax-hv-api.txt | 28 …separate Completion Area and, unless execution order is specifically restricted through the use of…
29 …conditional flags, the execution order of submitted CCBs is arbitrary. Likewise, the time to compl…
131 referenced by a CCB must be pinned in memory until the CCB either completes execution or is killed
134 execution.
211 to conditionally execute based on the successful execution of the closest CCB marked with the Seria…
213 and Serial to allow execution chaining. The flags do NOT allow fan-out chaining, where multiple CCBs
541 minus 1. Command execution stops
544 minus 1. Command execution stops
549 minus 1. Command execution stops
909 …by the virtual machine, simply updates the completion area with its execution status. The CCB may …
[all …]
|
| /linux-5.10/tools/perf/pmu-events/arch/x86/skylake/ |
| D | memory.json | 38 …"BriefDescription": "Number of times an HLE transactional execution aborted due to NoAllocatedElis…
48 …"BriefDescription": "Number of times an HLE transactional execution aborted due to XRELEASE lock n…
58 …"BriefDescription": "Number of times an HLE transactional execution aborted due to an unsupported …
77 …ay cause a transactional abort was executed. Since this is the count of execution, it may not alwa…
97 …"BriefDescription": "Counts the number of times an instruction execution caused the transactional …
165 "BriefDescription": "Execution stalls while L3 cache miss demand load is outstanding.",
197 "BriefDescription": "Number of times an HLE execution started.",
207 "BriefDescription": "Number of times an HLE execution successfully committed",
218 …"BriefDescription": "Number of times an HLE execution aborted due to any reasons (multiple categor…
227 …"BriefDescription": "Number of times an HLE execution aborted due to various memory events (e.g., …
[all …]
|
| /linux-5.10/tools/perf/pmu-events/arch/s390/cf_z15/ |
| D | extended.json | 91 …"PublicDescription": "A TEND instruction has completed in a constrained transactional-execution mo…
98 …cDescription": "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 …cDescription": "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…
|
| /linux-5.10/Documentation/ia64/ |
| D | fsys.rst | 13 execution to the ia64 linux kernel. We call this mode the
14 "fsys-mode". To recap, the normal states of execution are:
28 interruption-handlers start execution in. The user-level
34 - execution is at privilege level 0 (most-privileged)
41 - execution is interruptible and preemptible (an fsys-mode handler
147 execution may be pre-empted and resumed on another CPU at any given
169 fast system call execution (while fully preserving system call
221 such that execution resumes in the gate page at
240 state such that execution resumes in the gate page at
|
| /linux-5.10/drivers/gpu/drm/i915/ |
| D | i915_request.h | 75 * I915_FENCE_FLAG_PQUEUE - this request is ready for execution
77 * Using the scheduler, when a request is ready for execution it is put
111 * The execution of some requests should not be interrupted. This is
123 * execution all other active requests will have been preempted and
205 * It is used by the driver to then queue the request for execution.
492 * i915_request_is_ready - check if the request is ready for execution
497 * not want to start execution and read data before it is written. In practice,
500 * request into its queue and from there submit it for execution. So we
501 * can detect when a request is eligible for execution (and is under control
504 * Returns true if the request is ready for execution (it may be inflight),
|
| /linux-5.10/tools/perf/pmu-events/arch/x86/amdzen2/ |
| D | floating-point.json | 6 …p uOps. The number of operations (uOps) dispatched to each of the 4 FPU execution pipelines. This …
13 …"PublicDescription": "The number of operations (uOps) dispatched to each of the 4 FPU execution pi…
20 …"PublicDescription": "The number of operations (uOps) dispatched to each of the 4 FPU execution pi…
27 …"PublicDescription": "The number of operations (uOps) dispatched to each of the 4 FPU execution pi…
34 …"PublicDescription": "The number of operations (uOps) dispatched to each of the 4 FPU execution pi…
|
| /linux-5.10/drivers/tee/amdtee/ |
| D | Kconfig | 2 # AMD-TEE Trusted Execution Environment Configuration
8 This implements AMD's Trusted Execution Environment (TEE) driver.
|
| /linux-5.10/arch/powerpc/include/asm/nohash/32/ |
| D | mmu-44x.h | 47 #define PPC44x_TLB_UX 0x00000020 /* User execution */
50 #define PPC44x_TLB_SX 0x00000004 /* Super execution */
92 #define PPC47x_TLB2_UX 0x00000020 /* User execution */
95 #define PPC47x_TLB2_SX 0x00000004 /* Super execution */
|
12345678910>>...51