| /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/Documentation/ABI/testing/ |
| H A D | debugfs-driver-qat_telemetry | 66 exec_cpr<N> execution count of Compression slice N
68 exec_xlt<N> execution count of Translator slice N
70 exec_dcpr<N> execution count of Decompression slice N
72 exec_cnv<N> execution count of Compression and verify slice N
74 exec_dcprz<N> execution count of Decompression slice N
76 exec_pke<N> execution count of PKE N
78 exec_ucs<N> execution count of UCS slice N
81 exec_wat<N> execution count of Wireless Authentication
84 exec_wcp<N> execution count of Wireless Cipher slice N
86 exec_cph<N> execution count of Cipher slice N
[all …]
|
| /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.
|
| H 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/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/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
33 enabling/disabling of hardware support for the execution of these
34 instructions. Using hardware execution generally provides better
|
| /linux/Documentation/core-api/real-time/ |
| H A D | theory.rst | 19 This transformation places the majority of kernel execution contexts under the
22 becoming runnable and its actual execution on the CPU.
38 scheduler immediately selects it for execution if it has a higher priority than
81 task A can resume execution.
106 execution, those soft interrupt routines are invoked after the threaded handler
108 execution of the soft interrupt handler.
115 disabled, allowing the scheduler to preempt the current execution context and
|
| H A D | differences.rst | 44 execution into threaded context by different mechanisms. The goal is to keep
45 execution paths preemptible, allowing the scheduler to interrupt them when a
49 threaded, preemptible execution.
125 threads. To explicitly request execution in hard interrupt context on
164 On PREEMPT_RT systems, the execution model changes. Because irq_work callbacks
165 may acquire sleeping locks or have unbounded execution time, they are handled
178 RCU callbacks are invoked by default in softirq context. Their execution is
|
| /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 …]
|
| H 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/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
|
| H A D | timerlat-tracer.rst | 50 The ACTIVATION ID field serves to relate the *irq* execution to its
51 respective *thread* execution.
58 postponing the scheduler execution via preempt_disable(), scheduler
59 execution, or masking interrupts. Threads can also be delayed by the
110 by the IRQ execution (which indeed accounted for 12736 ns). But
|
| /linux/Documentation/gpu/ |
| H A D | msm-preemption.rst | 19 then resumes execution and fires an IRQ to let the kernel know the context
25 also done whenever a submission completes to make sure execution resumes on a
41 of state to be saved as the execution of userspace submitted IBs is never
98 execution of some packets in a ring and execute user commands with higher
|
| /linux/Documentation/trace/rv/ |
| H A D | runtime-verification.rst | 12 system's actual execution, comparing it against a formal specification of
82 reading the trace execution from a permanent storage system. *Online* monitors
83 process the trace during the execution of the system. Online monitors are said
85 execution, blocking the system during the event monitoring. On the other hand,
86 an *asynchronous* monitor has its execution detached from the system. Each type
|
| /linux/Documentation/driver-api/nfc/ |
| H 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/process/debugging/ |
| H A D | index.rst | 39 execution?
66 When timing does alter the outcome of the code execution using a simple
|
| /linux/fs/netfs/ |
| H A D | Kconfig | 20 execution as there are a quite a few stats gathered, and on a
55 execution as there are a quite a few stats gathered, and on a
|
| /linux/kernel/trace/rv/ |
| H A D | Kconfig | 34 actual execution, comparing it against a formal specification of
77 on the model's execution. By default, the monitors have
|
| /linux/Documentation/admin-guide/ |
| H 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/staging/ |
| H 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/drivers/gpu/drm/i915/ |
| H A D | Kconfig.profile | 128 alternate execution of each batch to ensure forward progress of
131 concurrent execution in order for them to proceed, e.g. they
133 is scheduled for execution for the timeslice duration, before
|
| /linux/Documentation/arch/sparc/oradax/ |
| H A 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 …]
|
| H 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/ |
| H 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/kernel/bpf/ |
| H A D | Kconfig | 63 execution of BPF instructions by the interpreter.
85 speculative execution side-channel vulnerabilities on unmitigated
|