Searched full:execution (Results 1 – 25 of 180) sorted by relevance
12345678
| /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 …]
|
| /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 …]
|
| /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
|
| /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
|
| /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 …]
|
| D | special-register-buffer-data-sampling.rst | 68 During execution of the RDRAND, RDSEED, or EGETKEY instructions, off-core
91 enclaves (including execution of RDRAND or RDSEED inside an enclave, as well
92 as EGETKEY execution).
146 This new microcode serializes processor access during execution of RDRAND,
|
| /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.
|
| /Documentation/filesystems/spufs/ |
| D | spu_run.rst | 28 uled to a physical SPU, it starts execution at the instruction pointer
31 Execution of SPU code happens synchronously, meaning that spu_run does
34 other SPUs, you need to create a new thread of execution first, e.g.
|
| /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
|
| /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 …]
|
| D | oracle-dax.rst | 38 requests to the available coprocessor execution units. A status code
42 is written by the coprocessor to provide execution status. No
52 completion of a request and resumption of execution of the requesting
124 Kills a CCB during execution. The CCB is guaranteed to not continue
137 Submission of an array of CCBs for execution
171 %asr28). This instruction is like pause in that it suspends execution
175 mwait terminates. This causes software to resume execution immediately
178 and resumption of execution may be just a few nanoseconds.
|
| /Documentation/userspace-api/ |
| D | unshare.rst | 29 as multiple execution contexts within a process. These kernels provide
126 unshare - disassociate parts of the process execution context
134 unshare() allows a process to disassociate parts of its execution
136 of execution context, such as the namespace, is shared by default
143 shared execution context without creating a new process.
315 4) Concurrent execution: Use shared memory segments and futex on
316 an address in the shm segment to synchronize execution of
|
| /Documentation/admin-guide/ |
| D | init.rst | 7 (listed roughly in order of execution) to load the init binary.
35 execution. To find out more, add code ``to init/main.c`` to display
|
| D | perf-security.rst | 32 execution metrics for various monitored parts of the system (e.g.,
34 uncore counters) without direct attribution to any execution context
37 4. Content of architectural execution context registers (e.g., RIP, RSP,
44 of execution context registers or data from process memory then access
|
| /Documentation/devicetree/bindings/crypto/ |
| D | qcom,prng.txt | 7 (Execution Environment) slice of prng
|
| /Documentation/scsi/ |
| D | advansys.rst | 78 execution of the driver.
85 of the driver execution image and add overhead to the execution of
153 size of the driver execution image and add minor overhead to
154 the execution of the driver.
|
| /Documentation/devicetree/bindings/arm/firmware/ |
| D | linaro,optee-tz.txt | 4 Execution Environment. The security can be provided with ARM TrustZone, but
|
| /Documentation/gpu/ |
| D | drm-mm.rst | 12 (TTM) and Graphics Execution Manager (GEM). TTM was the first DRM memory
24 share it. GEM has simpler initialization and execution requirements than
82 The Graphics Execution Manager (GEM)
92 The GEM userspace API is described in the `GEM - the Graphics Execution
108 - Command execution
109 - Aperture management at command execution time
115 Device-specific operations, such as command execution, pinning, buffer
332 Command Execution
336 command execution interface to clients. Client programs construct
|
| /Documentation/staging/ |
| D | speculation.rst | 11 employ speculative execution techniques such as branch prediction, performing
14 Typically speculative execution cannot be observed from architectural state,
|
| /Documentation/driver-api/thermal/ |
| D | cpu-cooling-api.rst | 78 - In running time the 'execution' behaviour (instruction types, memory
87 f(run) here represents the described execution behaviour and its
|
| /Documentation/devicetree/bindings/arm/msm/ |
| D | qcom,idle-state.txt | 21 execution. This state is defined as a generic ARM WFI state by the ARM cpuidle
30 sequence and would wait for interrupt, before restoring the cpu to execution
|
| /Documentation/ABI/testing/ |
| D | sysfs-devices-online | 17 After a successful execution of the bus type's .offline()
|
| /Documentation/virt/ |
| D | paravirt_ops.rst | 12 allows a single kernel binary to run on all supported execution environments
|
| /Documentation/x86/ |
| D | entry_64.rst | 90 entry interrupting kernel mode execution, then we know that the GS
92 user-space execution then we must do the SWAPGS.
|
| /Documentation/devicetree/bindings/riscv/ |
| D | cpus.yaml | 17 hart: A hardware execution context, which contains all the state
19 terminology is designed to disambiguate software's view of execution
|
12345678