Searched full:runtime (Results 1 – 25 of 222) sorted by relevance
123456789
| /Documentation/ABI/testing/ |
| D | sysfs-firmware-efi-runtime-map | 1 What: /sys/firmware/efi/runtime-map/
4 Description: Switching efi runtime services to virtual mode requires
5 that all efi memory ranges which have the runtime attribute
8 The efi runtime services can only be switched to virtual
14 /sys/firmware/efi/runtime-map/ is the directory the kernel
19 /sys/firmware/efi/runtime-map/0
20 /sys/firmware/efi/runtime-map/1
21 /sys/firmware/efi/runtime-map/2
22 /sys/firmware/efi/runtime-map/3
|
| D | sysfs-firmware-efi | 8 What: /sys/firmware/efi/runtime
11 Description: It shows the physical address of runtime service table entry in
35 Description: Displays the content of the Runtime Configuration Interface
|
| D | sysfs-devices-lpss_ltr | 18 This attribute is read-only. If the device's runtime PM status
30 This attribute is read-only. If the device's runtime PM status
42 This attribute is read-only. If the device's runtime PM status
|
| D | evm | 24 runtime. Not supported if HMAC validation and
26 31 Disable further runtime modification of EVM policy
67 to be added at runtime. Any signatures generated after
|
| D | sysfs-profiling | 5 /sys/kernel/profiling is the runtime equivalent
|
| D | sysfs-bus-iio-dfsdm-adc-stm32 | 8 provide information on the SPI clock frequency during runtime
|
| /Documentation/power/ |
| D | runtime_pm.rst | 2 Runtime Power Management Framework for I/O Devices
14 Support for runtime power management (runtime PM) of I/O devices is provided
19 used for queuing all work items related to runtime PM, because this allows
24 * A number of runtime PM fields in the 'power' member of 'struct device' (which
26 be used for synchronizing runtime PM operations with one another.
28 * Three device runtime PM callbacks in 'struct dev_pm_ops' (defined in
31 * A set of helper functions defined in drivers/base/power/runtime.c that can be
32 used for carrying out runtime PM operations in such a way that the
36 The runtime PM callbacks present in 'struct dev_pm_ops', the device runtime PM
38 runtime PM are described below.
[all …]
|
| D | pci.rst | 241 runtime GPEs.
357 2.3. Runtime Device Power Management
360 The PCI subsystem plays a vital role in the runtime power management of PCI
361 devices. For this purpose it uses the general runtime power management
362 (runtime PM) framework described in Documentation/power/runtime_pm.rst.
369 that are executed by the core runtime PM routines. It also implements the
370 entire mechanics necessary for handling runtime wakeup signals from PCI devices
489 state. Just like in the runtime PM case described above, the mechanism of
690 controlling the runtime power management of their devices.
697 however, doesn't allow one to define runtime power management callbacks and is
[all …]
|
| /Documentation/x86/x86_64/ |
| D | uefi.rst | 28 If EFI runtime services are expected, the following configuration should
44 - If some or all EFI runtime services don't work, you can try following
45 kernel command line parameters to turn off some or all EFI runtime
49 turn off all EFI runtime services
51 turn off EFI reboot runtime service
|
| /Documentation/scheduler/ |
| D | sched-deadline.rst | 52 SCHED_DEADLINE [18] uses three parameters, named "runtime", "period", and
54 "runtime" microseconds of execution time every "period" microseconds, and
55 these "runtime" microseconds are available within "deadline" microseconds
61 task actually receives "runtime" time units within "deadline" if a proper
66 that each task runs for at most its runtime every period, avoiding any
76 - Each SCHED_DEADLINE task is characterized by the "runtime",
80 a "remaining runtime". These two parameters are initially set to 0;
85 remaining runtime runtime
91 remaining runtime are re-initialized as
94 remaining runtime = runtime
[all …]
|
| D | sched-bwc.rst | 98 In case b) above, even though the child may have runtime remaining it will not
99 be allowed to until the parent's runtime is refreshed.
143 have remaining quota. This runtime discrepancy will be made up in the following
148 1. Limit a group to 1 CPU worth of runtime::
151 1 CPU worth of runtime every 250ms.
156 2. Limit a group to 2 CPUs worth of runtime on a multi-CPU machine
159 runtime every 500ms::
|
| D | sched-rt-group.rst | 31 system when the runtime is so small the system has difficulty making
102 * A run time of -1 specifies runtime == period, ie. no limit.
112 it. By setting runtime to -1 you'd get the old behaviour back.
161 * group A: period=100000us, runtime=50000us
165 * group B: period= 50000us, runtime=25000us
|
| /Documentation/driver-api/pm/ |
| D | devices.rst | 61 Runtime Power Management model:
75 the PM core are involved in runtime power management. As in the system
82 have been put into low-power states (at runtime), the effect may be very similar
84 synergies exist, so that several drivers using runtime PM might put the system
102 system sleep and runtime power management.
112 sufficient to remember that the last three methods are specific to runtime power
193 wakeup" used by runtime power management, although it may be supported by the
199 case, remote wakeup should always be enabled for runtime power management for
207 runtime power management. This flag, :c:member:`runtime_auto`, is initialized
209 or :c:func:`pm_runtime_forbid()`; the default is to allow runtime power
[all …]
|
| /Documentation/vm/ |
| D | zswap.rst | 40 can also be enabled and disabled at runtime using the sysfs interface.
41 An example command to enable zswap at runtime, assuming sysfs is mounted
46 When zswap is disabled at runtime it will stop storing pages that are
69 also be changed at runtime using the sysfs ``zpool`` attribute, e.g.::
102 It can also be changed at runtime using the sysfs "compressor"
107 When the zpool and/or compressor parameter is changed at runtime, any existing
123 disabled at runtime using the sysfs ``same_filled_pages_enabled``
128 When zswap same-filled page identification is disabled at runtime, it will stop
|
| D | page_owner.rst | 31 with page owner and page owner is disabled in runtime due to no enabling
32 boot option, runtime overhead is marginal. If disabled in runtime, it
33 doesn't require memory to store owner information, so there is no runtime
|
| /Documentation/driver-api/ |
| D | device_link.rst | 43 Another optional feature is runtime PM integration: By setting the
45 is instructed to runtime resume the supplier and keep it active
46 whenever and for as long as the consumer is runtime resumed.
87 shutdown ordering) and ``DL_FLAG_PM_RUNTIME`` to express that runtime PM
92 can be specified to runtime resume the supplier and prevent it from suspending
93 before the consumer is runtime suspended. ``DL_FLAG_AUTOREMOVE_CONSUMER``
129 :c:func:`device_link_add()` may cause the PM-runtime usage counter of the
134 link between these calls, in which case allowing the PM-runtime usage counter
136 suspended while the consumer is still PM-runtime-active and that has to be
138 runtime suspend at least once, or call :c:func:`pm_runtime_set_suspended()` for
[all …]
|
| /Documentation/admin-guide/pm/ |
| D | strategies.rst | 38 "runtime active" and that situation typically corresponds to the maximum power
40 as a whole is regarded as "runtime idle" which may be very close to a sleep
46 runtime idle in one go. For this reason, systems usually use less energy in
47 sleep states than when they are runtime idle most of the time.
|
| /Documentation/sound/designs/ |
| D | tracepoints.rst | 34 interaction between applications and ALSA PCM core. Once decided, runtime of
116 :c:type:`struct snd_pcm_hardware` and rules of constraints in the runtime. The
121 runtime as a default.
127 :c:type:`struct snd_pcm_hardware` type in the runtime, according to
130 of constraints into the runtime when several parameters have dependencies
158 and total number of rules added to the runtime. As an exception, the index 000
|
| /Documentation/devicetree/bindings/net/ |
| D | mediatek-bluetooth.txt | 57 - pinctrl-names: Should be "default", "runtime"
91 uart1_pins_runtime: uart1-runtime {
111 pinctrl-names = "default", "runtime";
|
| /Documentation/gpu/ |
| D | vkms.rst | 26 Runtime Configuration
93 - Add support for link status, so that compositors can validate their runtime
96 - All the hotplug handling describe under "Runtime Configuration".
|
| D | introduction.rst | 35 Instead locking should be check at runtime using e.g.
37 documentation than runtime noise this provides more value. And on top of
38 that runtime checks do need to be updated when the locking rules change,
|
| /Documentation/networking/ |
| D | devlink-params-mlxsw.txt | 10 Configuration mode: runtime
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-demux-pinctrl.txt | 6 runtime which may have a better feature set for a given task than another I2C
8 if your current runtime configuration hits an errata of the internal IP core.
135 enable them at runtime when needed.
|
| /Documentation/devicetree/bindings/serial/ |
| D | arm_sbsa_uart.txt | 4 cannot be adjusted at runtime, so it lacks a clock specifier here.
|
| /Documentation/trace/ |
| D | ftrace-design.rst | 312 some extra state when runtime patching arbitrary call sites, this is the
352 This might look a little odd at first, but keep in mind that we will be runtime
359 runtime patching. You'll need a little knowledge of your arch's opcodes in
371 There are two functions that are used to do runtime patching of arbitrary
373 is what helps us retain runtime performance when not tracing). The second is
384 The last function is used to do runtime patching of the active tracer. This
416 - ftrace_enable_ftrace_graph_caller() will runtime patch the
418 - ftrace_disable_ftrace_graph_caller() will runtime patch the
|
123456789