Searched full:running (Results 1 – 25 of 739) sorted by relevance
12345678910>>...30
| /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 | sfc.rst | 22 - running
26 - running
30 - running
33 - running
36 - running
39 - running
42 - running
45 - running
48 - running
51 - running
[all …]
|
| D | nfp.rst | 49 - stored, running
52 - stored, running
55 - stored, running
58 - stored, running
61 - stored, running
64 - stored, running
67 - stored, running
|
| D | bnxt.rst | 66 - stored, running
69 - stored, running
72 - stored, running
75 - running
78 - stored, running
81 - stored, running
|
| D | i40e.rst | 27 - running
32 - running
38 - running
42 - running
52 - running
56 - running
|
| D | etas_es58x.rst | 22 - running
23 - Version of the firmware running on the device. Also available
27 - running
28 - Version of the bootloader running on the device. Also available
|
| 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
|
| /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/scheduler/ |
| D | schedutil.rst | 33 resume running.
35 Using this we track 2 key metrics: 'running' and 'runnable'. 'Running'
38 two metrics are the same, but once there is contention for the CPU 'running'
49 for 50% at 2GHz, nor is running 50% on a LITTLE CPU the same as running 50% on
83 The result is that the above 'running' and 'runnable' metrics become invariant
97 though when running their expected utilization will be the same, they suffer a
98 (DVFS) ramp-up after they are running again.
101 Impulse Response (IIR) EWMA with the 'running' value on dequeue -- when it is
115 the runqueue keeps an max aggregate of these clamps for all running tasks.
127 The basis is the CPU runqueue's 'running' metric, which per the above it is
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-qat | 10 * up: the device is up and running
28 * sym;asym: the device is configured for running crypto
31 * dc: the device is configured for running compression services
34 * sym: the device is configured for running symmetric crypto
36 * asym: the device is configured for running asymmetric crypto
38 * asym;dc: the device is configured for running asymmetric
41 * sym;dc: the device is configured for running symmetric crypto
49 a device configured for running crypto services in order to
117 * dc: the ring pair is configured for running compression services
118 * sym: the ring pair is configured for running symmetric crypto
[all …]
|
| 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/virt/kvm/x86/ |
| D | running-nested-guests.rst | 4 Running nested guests with KVM
31 - L0 – level-0; the bare metal host, running KVM
33 - L1 – level-1 guest; a VM running on L0; also called the "guest
34 hypervisor", as it itself is capable of running KVM.
36 - L2 – level-2 guest; a VM running on L1, this is the "nested guest"
43 hypervisor running on bare metal, adding another layer and
45 metal, running the LPAR hypervisor), L1 (host hypervisor), L2
63 multiple nested guests (level-2 guests), running different OSes, on
83 In case you are running a Linux kernel older than v4.19, to enable
139 .. note:: If you suspect your L2 (i.e. nested guest) is running slower,
[all …]
|
| /Documentation/trace/rv/ |
| D | monitor_wwnr.rst | 4 - Name: wwrn - wakeup while not running
26 | running | -+
29 This model is broken, the reason is that a task can be running
38 running.
|
| /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/virt/ |
| D | ne_overview.rst | 15 can be separated from other applications running in the same VM. This
24 carved out of the primary VM. Each enclave is mapped to a process running in the
29 1. An enclave abstraction process - a user space process running in the primary
39 hypervisor running on the host where the primary VM is running. The Nitro
42 2. The enclave itself - a VM running on the same host as the primary VM that
90 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/dev-tools/kunit/ |
| D | faq.rst | 25 Does KUnit support running on architectures other than UML?
76 2. Instead of running ``kunit.py run``, try running ``kunit.py config``,
80 3. Running the UML kernel directly can often reveal issues or error messages,
81 ``kunit_tool`` ignores. This should be as simple as running ``./vmlinux``
89 around, so you can see what config was used after running ``kunit.py run``.
93 5. Try to run ``make ARCH=um defconfig`` before running ``kunit.py run``. This
95 6. Finally, try running KUnit outside UML. KUnit and KUnit tests can be
|
| D | run_wrapper.rst | 4 Running tests with kunit_tool
69 generated by running ``make savedefconfig``), used for running a
90 set in the kernel ``.config`` before running the tests. It warns if we
101 Configuring, building, and running tests
106 When running kunit_tool, from a ``.kunitconfig``, we can generate a
128 The ``run`` command discussed in section: **Running tests with kunit_tool**,
129 is equivalent to running the above three commands in sequence.
135 format. When running tests, kunit_tool parses this output and prints
170 Running tests on QEMU
173 kunit_tool supports running tests on qemu as well as
[all …]
|
| D | running_tips.rst | 4 Tips For Running KUnit Tests
10 Running from any directory
25 Running a subset of tests
154 Running tests manually
157 Running tests without using ``kunit.py run`` is also an important use case.
161 As running the tests under UML is fairly straightforward (configure and compile
166 Running built-in tests
192 Running tests as modules
238 Regardless of how you're running your tests, you can enable
273 # Reset coverage counters before running the test.
[all …]
|
| /Documentation/bpf/ |
| D | bpf_prog_run.rst | 4 Running BPF programs from userspace
7 This document describes the ``BPF_PROG_RUN`` facility for running BPF programs
52 Running XDP programs in "live frame mode"
55 The ``BPF_PROG_RUN`` command has a separate mode for running live XDP programs,
63 XDP program many times (suitable for, e.g., running as a traffic generator),
71 in the syscall parameters when running in this mode will be rejected. In
91 - When running the program with multiple repetitions, the execution will happen
|
| /Documentation/admin-guide/hw-vuln/ |
| D | core-scheduling.rst | 9 workloads may benefit from running on the same core as they don't need the same
16 A cross-HT attack involves the attacker and victim running on different Hyper
91 scheduling group and share it with already running tasks.
100 siblings of a core such that all the selected tasks running on a core are
132 considered depending on whether a VM or a regular usermode process was running
157 and are considered system-wide trusted. The forced-idling of siblings running
168 concurrently or kernel could be running concurrently with a task not trusted by
176 cause an attacker task to start running on a CPU before its siblings receive the
186 running in user mode and the others running in kernel mode. Even though all
188 code on behalf of a task, it cannot trust the code running in the
[all …]
|
| /Documentation/virt/geniezone/ |
| D | introduction.rst | 40 The gzvm hypervisor emulates a virtual mobile platform for guest OS running on
58 All interrupts during some guest VMs running are handled by GenieZone
60 In case there's no guest VM running, physical interrupts are handled by host
78 controls the vCPU lifecycle including creating, running and destroying.
|
12345678910>>...30