| /linux/Documentation/firmware-guide/acpi/ |
| A D | method-tracing.rst | 86 [ 0.186630] exdebug-0398 ex_trace_point : Opcode Begin [0xf5905c88:If] 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.
94 [ 0.188146] exdebug-0398 ex_trace_point : Opcode Begin [0xf5905f60:One] execution.
95 [ 0.188334] exdebug-0398 ex_trace_point : Opcode End [0xf5905f60:One] execution.
97 [ 0.188712] exdebug-0398 ex_trace_point : Opcode End [0xf5905c88:If] execution.
201 during any method execution will be logged.
207 during method execution of "trace_method_name" will be logged.
213 during method execution of "trace_method_name" will be logged only once.
219 during method/opcode execution of "trace_method_name" will be logged.
[all …]
|
| /linux/Documentation/core-api/ |
| 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
44 those very limited execution contexts leading to various problems
71 In order to ease the asynchronous execution of functions a new
126 without losing execution bandwidth.
146 for execution contexts to free up.
187 new work item starts execution until thawed.
192 execution context regardless of memory pressure.
209 execution is regulated by the system scheduler.
[all …]
|
| /linux/Documentation/arm64/ |
| A D | legacy_instructions.rst | 9 the instruction execution in hardware.
12 (/proc/sys/abi). The following explains the different execution
33 enabling/disabling of hardware support for the execution of these
34 instructions. Using hardware execution generally provides better
|
| /linux/Documentation/admin-guide/hw-vuln/ |
| 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.
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.
98 execution can be measured to infer data values.
195 execution.
[all …]
|
| A D | special-register-buffer-data-sampling.rst | 69 During execution of the RDRAND, RDSEED, or EGETKEY instructions, off-core
92 enclaves (including execution of RDRAND or RDSEED inside an enclave, as well
93 as EGETKEY execution).
147 This new microcode serializes processor access during execution of RDRAND,
|
| /linux/Documentation/ABI/testing/ |
| A D | sysfs-devices-platform-soc-ipa | 55 attributes describing properties of the modem execution
65 the modem execution environment. The "rx" is from the
76 the modem execution environment. The "tx" is from the
|
| /linux/Documentation/trace/ |
| 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
130 the thread_noise, starting a irq_noise. When the IRQ ends its execution,
133 IRQ execution. This logic is valid for all sources of noise.
145 timer IRQ execution. The first event is not part of the noise because
151 before and after any interference execution. This justifies the dual
|
| A D | timerlat-tracer.rst | 50 ID field serves to relate the *irq* execution to its respective *thread*
51 execution.
58 postponing the scheduler execution via preempt_disable(), scheduler
59 execution, or masking interrupts. Threads can also be delayed by the
109 by the IRQ execution (which indeed accounted for 12736 ns). But
|
| /linux/Documentation/ia64/ |
| A 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/Documentation/driver-api/nfc/ |
| A D | nfc-hci.rst | 28 HCI uses 2 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/Documentation/userspace-api/ |
| A 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
|
| /linux/drivers/gpu/drm/i915/ |
| A D | Kconfig.profile | 110 alternate execution of each batch to ensure forward progress of
113 concurrent execution in order for them to proceed, e.g. they
115 is scheduled for execution for the timeslice duration, before
|
| /linux/Documentation/staging/ |
| A D | speculation.rst | 11 employ speculative execution techniques such as branch prediction, performing
14 Typically speculative execution cannot be observed from architectural state,
|
| /linux/kernel/bpf/ |
| A D | Kconfig | 59 execution of BPF instructions by the interpreter.
77 speculative execution side-channel vulnerabilities on unmitigated
|
| /linux/Documentation/admin-guide/ |
| A 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
|
| /linux/Documentation/sparc/oradax/ |
| A D | dax-hv-api.txt | 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.
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
980 0 1 CCB execution status
1003 0x8 Command execution timeout
1024 The CCB completion area should be treated as read-only by guest software. The CCB execution status
[all …]
|
| A 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.
|
| /linux/Documentation/scsi/ |
| A 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.
|
| /linux/tools/testing/selftests/firmware/ |
| A D | settings | 4 # normal execution should be 2 * 3 * 2 * 2 * 5 = 120 seconds for those alone.
|
| /linux/arch/arm/vfp/ |
| A D | entry.S | 18 @ r2 = PC value to resume execution after successful emulation
|
| /linux/Documentation/devicetree/bindings/riscv/ |
| A 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
|
| /linux/Documentation/x86/ |
| A D | exception-tables.rst | 51 (i.e. regs->eip) to find an address where the execution can continue
53 return address (again regs->eip) and returns. The execution will
207 in the normal execution path. They are located in a different section
291 #. execution continues in the fault handling code.
294 c) execution continues at local label 2 (address of the
|
| /linux/tools/testing/selftests/tc-testing/creating-plugins/ |
| A D | AddingPlugins.txt | 71 the execution stage and a string which is the actual command to be
73 execution.
|
| /linux/fs/netfs/ |
| A D | Kconfig | 20 execution as there are a quite a few stats gathered, and on a
|
| /linux/Documentation/filesystems/spufs/ |
| A D | spu_run.rst | 28 uled to a physical SPU, it starts execution at the instruction pointer
34 other SPUs, you need to create a new thread of execution first, e.g.
|