Searched full:executing (Results 1 – 25 of 113) sorted by relevance
12345
| /Documentation/ABI/testing/ |
| D | debugfs-olpc | 7 A generic interface for executing OLPC Embedded Controller commands and
14 To read the response (if any), read from the generic node after executing
|
| D | sysfs-kernel-fscaps | 7 when executing a binary
|
| D | sysfs-power | 351 number of times executing "resume" callbacks of
359 the number of times executing "early resume" callbacks
367 the number of times executing "noirq resume" callbacks
375 the number of times executing "suspend" callbacks
383 the number of times executing "late suspend" callbacks
391 the number of times executing "noirq suspend" callbacks
|
| /Documentation/admin-guide/pm/ |
| D | intel-speed-select.rst | 68 Executing on CPU model: X
101 Executing on CPU model: X
126 Executing on CPU model: X
145 Executing on CPU model: X
174 Executing on CPU model: X
200 Executing on CPU model: X
245 Executing on CPU model: X
323 Executing on CPU model: X
351 Executing on CPU model: X
370 Executing on CPU model: X
[all …]
|
| D | strategies.rst | 42 then it takes much less time and effort to start executing user space code than
|
| /Documentation/devicetree/bindings/mtd/ |
| D | davinci-nand.txt | 27 - ti,davinci-mask-ale: mask for ALE. Needed for executing address
33 - ti,davinci-mask-cle: mask for CLE. Needed for executing command
|
| /Documentation/driver-api/nfc/ |
| D | nfc-hci.rst | 30 - one for executing commands : nfc_hci_msg_tx_work(). Only one command
31 can be executing at any given moment.
223 Workflow executing an HCI command (using shdlc)
226 Executing an HCI command can easily be performed synchronously using the
303 error from a lower layer, HCI will either complete the currently executing
305 executing.
|
| /Documentation/ABI/stable/ |
| D | sysfs-devices-system-cpu | 18 This default value is used when the kernel is executing and
|
| /Documentation/RCU/ |
| D | NMI-RCU.rst | 84 currently executing on some other CPU. We therefore cannot free
97 executing.
|
| /Documentation/devicetree/bindings/mtd/partitions/ |
| D | brcm,trx.txt | 15 executing. Other partitions can be used for operating system purposes. This is
|
| /Documentation/devicetree/ |
| D | of_unittest.rst | 12 This document explains how the test data required for executing OF unittest
31 the test data required for executing the unit tests automated in
108 Before executing OF unittest, it is required to attach the test data to
|
| /Documentation/userspace-api/ |
| D | seccomp_filter.rst | 95 Results in the entire process exiting immediately without executing
100 Results in the task exiting immediately without executing the
106 task without executing the system call. ``siginfo->si_call_addr``
123 to userland as the errno without executing the system call.
132 notify a ``ptrace()``-based tracer prior to executing the system
|
| /Documentation/core-api/ |
| D | this_cpu_ops.rst | 9 variables associated with the *currently* executing processor. This is
33 data specific to the currently executing processor. Only the current
136 of the per cpu variable that belongs to the currently executing
226 change the processor we are executing on then there is no reason to
|
| /Documentation/vm/ |
| D | page_frags.rst | 25 to be disabled when executing the fragment allocation.
|
| /Documentation/parisc/ |
| D | registers.rst | 75 C (code address translation) 1, 0 while executing real-mode code
77 M (HPMC mask) 0, 1 while executing HPMC handler*
84 D (Data address translation) 1, 0 while executing real-mode code
|
| /Documentation/admin-guide/ |
| D | perf-security.rst | 183 monitoring. CPU and system events happened when executing either in
192 happened when executing either in user or in kernel space can be
199 system events happened when executing in user space only can be
|
| D | cpu-load.rst | 48 system is executing the idle handler), but in reality the load is
|
| /Documentation/ide/ |
| D | ide-tape.rst | 54 other device while the tape is busy executing a command. The
|
| /Documentation/admin-guide/hw-vuln/ |
| D | special-register-buffer-data-sampling.rst | 77 #. Executing RDRAND at the same time on multiple logical processors will be
81 #. Executing RDRAND, RDSEED or EGETKEY will delay memory accesses from other
|
| /Documentation/arm64/ |
| D | booting.rst | 210 executing on.
212 time whenever the kernel is executing.
220 all CPUs the kernel is executing on, and must stay constant
|
| /Documentation/hwmon/ |
| D | fam15h_power.rst | 93 i. Determine the ratio of Tsample to Tref by executing CPUID Fn8000_0007.
|
| /Documentation/scheduler/ |
| D | sched-capacity.rst | 103 Executing the same workload as described in 1.3.1, which each CPU running at its
144 spends more time sleeping than executing. Variable CPU frequencies and
170 behaviour (i.e. executing the same amount of work) in both executions.
192 Executing a given periodic workload on each CPU at their maximum frequency would
|
| /Documentation/accounting/ |
| D | delay-accounting.rst | 111 Get delays seen in executing a given simple command::
|
| /Documentation/devicetree/bindings/arm/msm/ |
| D | qcom,idle-state.txt | 23 configured to execute this state by default and after executing every other
|
| /Documentation/ia64/ |
| D | fsys.rst | 70 to by "regs" was executing in user mode (privilege level 3).
72 executing on the user-level stack(s). Finally, fsys_mode() returns
73 TRUE if the CPU state pointed to by "regs" was executing in fsys-mode.
|
12345