Searched full:running (Results 1 – 25 of 577) sorted by relevance
12345678910>>...24
| /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/networking/devlink/ |
| D | nfp.rst | 46 - stored, running
49 - stored, running
52 - stored, running
55 - stored, running
58 - stored, running
61 - stored, running
64 - stored, running
|
| D | bnxt.rst | 64 - stored, running
67 - stored, running
70 - stored, running
73 - running
76 - stored, running
79 - stored, running
|
| D | ice.rst | 27 - running
32 - running
38 - running
42 - running
52 - running
56 - running
61 - running
67 - running
73 - running
79 - running
[all …]
|
| D | devlink-flash.rst | 71 (``fixed``, ``running``, ``stored``).
79 ``running`` and ``stored`` firmware versions identify the firmware running
103 if $want_fw_vers != devlink-dev-info['running']:
108 if $want_fw_vers != devlink-dev-info['running']:
112 if $want_fw_vers != devlink-dev-info['running']:
|
| D | ionic.rst | 22 - running
23 - Version of firmware running on the device
|
| D | devlink-info.rst | 69 * - ``running``
70 - Group for information about currently running software/firmware.
82 components stored on the flash should feature in both the ``running`` and
86 ``/lib/firmware``) only the running version should be reported via
119 ``bundle_id`` can appear in both ``running`` and ``stored`` versions,
|
| /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:
54 Description: If running under Xen:
63 Description: If running under Xen:
71 Description: If running under Xen:
80 Description: If running under Xen:
87 Description: If running under Xen:
95 Description: If running under Xen:
[all …]
|
| /Documentation/virt/kvm/ |
| D | running-nested-guests.rst | 2 Running nested guests with KVM
29 - L0 – level-0; the bare metal host, running KVM
31 - L1 – level-1 guest; a VM running on L0; also called the "guest
32 hypervisor", as it itself is capable of running KVM.
34 - L2 – level-2 guest; a VM running on L1, this is the "nested guest"
41 hypervisor running on bare metal, adding another layer and
43 metal, running the LPAR hypervisor), L1 (host hypervisor), L2
61 multiple nested guests (level-2 guests), running different OSes, on
81 In case you are running a Linux kernel older than v4.19, to enable
137 .. note:: If you suspect your L2 (i.e. nested guest) is running slower,
[all …]
|
| /Documentation/driver-api/thermal/ |
| D | cpu-idle-cooling.rst | 83 running
95 cycle (aka the cooling device state), the running duration can be
111 running
125 running
160 (Ptarget) resulting in an amount of time running at full power on a
164 P(opp)target = ((Trunning x (P(opp)running) + (Tidle x P(opp)idle)) /
169 Tidle = Trunning x ((P(opp)running / P(opp)target) - 1)
171 At this point if we know the running period for the CPU, that gives us
173 injection duration, we can compute the running duration with::
175 Trunning = Tidle / ((P(opp)running / P(opp)target) - 1)
[all …]
|
| /Documentation/ABI/testing/ |
| 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:
34 Description: If running under Xen:
43 Description: If running under Xen:
|
| 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.
|
| /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/dev-tools/kunit/ |
| D | faq.rst | 25 Does KUnit support running on architectures other than UML?
71 1. Try running ``./tools/testing/kunit/kunit.py run`` with the ``--raw_output``
74 2. Instead of running ``kunit.py run``, try running ``kunit.py config``,
78 3. Running the UML kernel directly can often reveal issues or error messages
79 kunit_tool ignores. This should be as simple as running ``./vmlinux`` after
87 around, so you can see what config was used after running ``kunit.py run``.
91 5. Try to run ``make ARCH=um defconfig`` before running ``kunit.py run``. This
93 6. Finally, try running KUnit outside UML. KUnit and KUnit tests can be
|
| /Documentation/virt/ |
| D | ne_overview.rst | 15 can be separated from other applications running in the same VM. This
21 process running in the primary VM, that communicates with the NE driver via an
26 1. An enclave abstraction process - a user space process running in the primary
36 hypervisor running on the host where the primary VM is running. The Nitro
39 2. The enclave itself - a VM running on the same host as the primary VM that
87 running in the primary VM via a poll notification mechanism. Then the user space
|
| /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/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.
|
| /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/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
279 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/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
140 Running installed selftests
179 tests by using variables specified in `Running a subset of selftests`_
|
12345678910>>...24