Searched full:running (Results 1 – 25 of 518) sorted by relevance
12345678910>>...21
| /Documentation/scsi/scsi_transport_srp/ |
| D | rport_state_diagram.dot | 2 node [shape = doublecircle]; running lost;
7 running_rta [ label = "running;\nreconnect\ntimer\nactive" ];
9 running [ label = "running;\nreconnect\ntimer\nstopped" ];
14 …running -> running_rta [ label = "fast_io_fail_tmo = off and\ndev_loss_tmo = off;\nsrp_start_tl_f…
15 …running_rta -> running [ label = "fast_io_fail_tmo = off and\ndev_loss_tmo = off;\nreconnecting s…
16 …running -> blocked [ label = "fast_io_fail_tmo >= 0 or\ndev_loss_tmo >= 0;\nsrp_start_tl_fail_tim…
17 …running -> failfast [ label = "fast_io_fail_tmo = off and\ndev_loss_tmo = off;\nreconnecting fail…
21 blocked -> running [ label = "reconnecting\nsucceeded" ];
23 failfast -> running [ label = "reconnecting\nsucceeded" ];
24 running -> lost [ label = "srp_stop_rport_timers()" ];
|
| /Documentation/ABI/stable/ |
| D | sysfs-hypervisor-xen | 5 Description: If running under Xen:
14 Description: If running under Xen:
23 Description: If running under Xen:
32 Description: If running under Xen:
51 Description: If running under Xen:
60 Description: If running under Xen:
68 Description: If running under Xen:
77 Description: If running under Xen:
84 Description: If running under Xen:
92 Description: If running under Xen:
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-remoteproc | 9 To change the running firmware, ensure the remote processor is
21 "running"
30 "running" is the normal state of an available remote processor
44 Writing "start" will attempt to start the processor running the
47 transition to "running" state.
|
| D | sysfs-platform-chipidea-usb-otg | 7 the application running on the A-device wants to use the bus,
15 Reading: returns 1 if the application running on the A-device
24 application running on the A-device wants to power down
39 that the application running on the B-device wants to use the
45 Reading: returns if the application running on the B device
|
| D | sysfs-hypervisor-xen | 5 Description: If running under Xen:
16 Description: If running under Xen:
31 Description: If running under Xen:
40 Description: If running under Xen:
|
| D | procfs-concurrent_time | 7 active while the uid's task was running.
16 with that policy that were active while the uid's task was running.
|
| /Documentation/ia64/ |
| D | mca.rst | 43 * If an MCA/INIT event occurs while the kernel was running (not user
67 running or not. That is, whether it is on a cpu or is blocked. The
70 INIT event are no longer running, they have been converted to blocked
72 rendezvous interrupt are still running on their normal kernel stacks!
78 no longer running on that cpu. That gives us a decent chance of
83 failed, not on the task that was originally running. Again this
85 own stack as running on that cpu. Then a recursive error gets a
144 * i386 backtrace is not very sensitive to whether a process is running
146 running or not.
150 What happens when MCA/INIT is delivered what a cpu is running user
[all …]
|
| /Documentation/driver-api/dmaengine/ |
| D | pxa_dma.rst | 10 is queued even on a running DMA channel.
15 stop and restart, but is submitted on a "running channel". The other
25 c) Channel running state
26 A driver should be able to query if a channel is running or not. For the
30 know if a channel is in running or stopped state.
71 Suppose the running chain is:
107 this specific case if the DMA is already running in aligned mode.
117 any lock to find out what is the latest completed transfer in a running
139 currently running descriptor.
150 - a driver issued tx1+tx2 => channel is running in aligned mode
|
| /Documentation/devicetree/bindings/firmware/ |
| D | intel,stratix10-svc.txt | 11 Layer 3) can interface with SDM. All software entities running on other
15 Intel Stratix10 service layer driver, running at privileged exception level
19 code running in EL3.
|
| /Documentation/devicetree/bindings/sound/ |
| D | soc-ac97link.txt | 8 "ac97-running": AC97-link is active
20 pinctrl-names = "default", "ac97-running", "ac97-reset", "ac97-warm-reset";
|
| /Documentation/devicetree/bindings/timer/ |
| D | brcm,bcm2835-system-timer.txt | 4 single 64-bit free running counter. Each channel has an output compare
6 free running counter values, and generates an interrupt.
|
| D | snps,archs-rtc.txt | 1 Synopsys ARC Free Running 64-bit Local Timer for ARC HS CPUs
|
| D | snps,archs-gfrc.txt | 1 Synopsys ARC Free Running 64-bit Global Timer for ARC HS CPUs
|
| /Documentation/core-api/ |
| D | cachetlb.rst | 44 the TLB. After running, this interface must make sure that
46 'mm' will be visible to the cpu. That is, after running,
57 address translations from the TLB. After running, this
61 running, there will be no entries in the TLB for 'mm' for
83 After running, this interface must make sure that any previous
86 is, after running, there will be no entries in the TLB for
140 the caches. That is, after running, there will be no cache
149 the caches. That is, after running, there will be no cache
162 addresses from the cache. After running, there will be no
190 After running, there will be no entries in the cache for
[all …]
|
| /Documentation/timers/ |
| D | no_hz.rst | 25 are running realtime applications or certain types of HPC
52 However, if you are instead running a light workload with long idle
56 are running light workloads, you should therefore read the following
59 In addition, if you are running either a real-time workload or an HPC
76 A battery-powered device running a CONFIG_HZ_PERIODIC=y kernel would
78 same device running a CONFIG_NO_HZ_IDLE=y kernel. A mainframe running
95 be "dyntick-idle", "in dyntick-idle mode", "in nohz mode", or "running
131 (This is not an issue for CONFIG_NO_HZ_IDLE=y because there are no running
151 adaptive ticks without also running dyntick idle. This dependency
281 running task's timeslice expires, which is almost always way
|
| /Documentation/leds/ |
| D | leds-lp55xx.rst | 15 Program memory for running LED patterns
55 - Program memory address access for running patterns
60 LP55xx family devices have the internal program memory for running
80 Select which engine is used for running program
166 The sequence of running the program data is common.
222 To stop running pattern::
|
| /Documentation/accounting/ |
| D | cgroupstats.rst | 29 sleeping 1, blocked 0, running 1, stopped 0, uninterruptible 0
31 sleeping 155, blocked 0, running 1, stopped 0, uninterruptible 2
|
| /Documentation/admin-guide/mm/ |
| D | userfaultfd.rst | 58 requested uffdio_api.api is spoken also by the running kernel and the
116 externalization consisting of a virtual machine running with part or
125 aren't waiting for userfaults (i.e. network bound) can keep running in
139 the QEMU running in the destination node runs UFFDIO_COPY|ZEROPAGE
150 After the QEMU postcopy thread (running in the destination node) gets
156 migration thread in the QEMU running in the destination node will
165 the QEMU running in the source node to know which pages are still
|
| /Documentation/dev-tools/ |
| D | kselftest.rst | 26 Running the selftests (hotplug tests are run in limited mode)
44 running tests. To locate output files in a separate directory two syntaxes
46 kernel src. This is applicable to "Running a subset of selftests" section
64 to "Running a subset of selftests" section below.
70 Running a subset of selftests
111 Running the full range hotplug selftests
142 Running installed selftests
|
| /Documentation/admin-guide/LSM/ |
| D | Yama.rst | 16 running state of any of their processes. For example, if one application
18 attach to other running processes (e.g. Firefox, SSH sessions, GPG agent,
52 process running under the same uid, as long as it is dumpable (i.e.
|
| /Documentation/driver-api/thermal/ |
| D | cpu-cooling-api.rst | 73 - The time the processor spends running, consuming dynamic power, as
78 - In running time the 'execution' behaviour (instruction types, memory
103 running time dynamic power coefficient in fundamental units of
|
| /Documentation/RCU/ |
| D | UP.rst | 97 UP systems, including PREEMPT SMP builds running on UP systems.
100 Why can't synchronize_rcu() return immediately on UP systems running
137 running preemptable RCU?
143 that other thread when it started running again.
|
| /Documentation/s390/ |
| D | 3270.rst | 45 running the configuration script (config3270.sh, in this directory).
52 one another. ReIPL as soon as possible after running the configuration
146 running the emulator on your PC or workstation. You would use
206 down. When it fills, the status area changes from "Linux Running" to
214 The status area initializes to "Linux Running" to give you a warm
221 Running" and nothing typed, the application receives a newline.)
239 PA1 causes a SIGINT to the currently running application. You may do
|
| /Documentation/virt/kvm/arm/ |
| D | hyp-abi.txt | 4 hypervisor layer when running Linux as a hypervisor (for example
6 hypervisor when running as a guest (under Xen, KVM or any other
|
| /Documentation/firmware-guide/acpi/ |
| D | method-customizing.rst | 42 b) disassemble the table by running "iasl -d dsdt.dat".
63 g) override the old method via the debugfs by running
81 .. note:: We can use a kernel with multiple custom ACPI method running,
|
12345678910>>...21