Searched refs:scenarios (Results 1 – 25 of 80) sorted by relevance
1234
| /Linux-v5.10/Documentation/RCU/ |
| D | torture.rst | 178 complete all the scenarios in two batches, reducing the time to complete
185 Not all changes require that all scenarios be run. For example, a change
186 to Tree SRCU might run only the SRCU-N and SRCU-P scenarios using the
188 Large systems can run multiple copies of of the full set of scenarios,
199 Or 28 concurrent instances of each of two eight-CPU scenarios::
241 Files pertaining to all scenarios in a run reside in the top-level
273 As of v5.4, a successful run with the default set of scenarios produces
|
| /Linux-v5.10/Documentation/ABI/obsolete/ |
| D | sysfs-class-dax | 15 what fault scenarios are supported.
|
| /Linux-v5.10/Documentation/devicetree/bindings/timer/ |
| D | andestech,atcpit100-timer.txt | 10 multi-function timer and provide the following usage scenarios:
|
| /Linux-v5.10/Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-palmas.txt | 43 scenarios. So for GPIO7 if ti,palmas-override-powerhold is set
46 power off scenarios the driver will over ride the mux value.
|
| /Linux-v5.10/Documentation/ABI/testing/ |
| D | sysfs-bus-iio-lptimer-stm32 | 47 In quadrature mode, encoder counting scenarios are as follows:
|
| /Linux-v5.10/Documentation/livepatch/ |
| D | system-state.rst | 82 3. Supported scenarios
87 scenarios:
|
| D | cumulative-patches.rst | 86 This might be seen as a limitation in some scenarios. But it makes life
|
| /Linux-v5.10/drivers/cpuidle/ |
| D | Kconfig | 72 host via halt_poll_ns for some scenarios).
|
| /Linux-v5.10/Documentation/admin-guide/hw-vuln/ |
| D | l1tf.rst | 65 Attack scenarios
182 scenarios where guest VMEXIT/VMENTER are rare the performance impact is
185 application scenarios might still suffer from a high VMEXIT rate.
239 scenarios.
262 configuration and the scenarios which run on the system. While for some
611 analyze the risk for their scenarios and make the appropriate
615 kind of scenarios.
|
| D | mds.rst | 64 Attack scenarios
132 This is done to address virtualization scenarios where the host has the
|
| D | tsx_async_abort.rst | 69 Attack scenarios
119 This is done to address virtualization scenarios where the host has the
|
| /Linux-v5.10/Documentation/networking/ |
| D | tcp-thin.rst | 11 effective. In time-dependent scenarios (like online games, control
|
| /Linux-v5.10/drivers/pinctrl/ |
| D | pinctrl-pistachio.c | 77 const int *scenarios; member
504 .scenarios = pistachio_##_name##_scenarios, \
969 if (pf->scenarios) { in pistachio_pinmux_enable()
971 if (pf->scenarios[i] == group) in pistachio_pinmux_enable()
|
| /Linux-v5.10/Documentation/powerpc/ |
| D | vcpudispatch_stats.rst | 11 scenarios, vcpus may be dispatched on a different processor chip (away
|
| /Linux-v5.10/fs/erofs/ |
| D | Kconfig | 10 blocks, inline xattrs/data, etc.) for scenarios which need
|
| /Linux-v5.10/Documentation/sound/hd-audio/ |
| D | dp-mst.rst | 47 So there are the following scenarios:
|
| /Linux-v5.10/Documentation/fb/ |
| D | deferred_io.rst | 34 It may be the case that this is useful in other scenarios as well. Paul Mundt
|
| /Linux-v5.10/Documentation/admin-guide/pm/ |
| D | strategies.rst | 49 Moreover, the two power management strategies address different usage scenarios.
|
| /Linux-v5.10/Documentation/bpf/ |
| D | prog_sk_lookup.rst | 19 BPF sk_lookup program type was introduced to address setup scenarios where
|
| /Linux-v5.10/Documentation/virt/kvm/ |
| D | running-nested-guests.rst | 54 There are several scenarios where nested KVM can be useful, to name a
201 scenarios should work even on AMD systems:
|
| /Linux-v5.10/Documentation/x86/ |
| D | mds.rst | 101 As a special quirk to address virtualization scenarios where the host has
124 scenarios where the host has the updated microcode but the
|
| D | tsx_async_abort.rst | 48 scenarios where the host has the updated microcode but the
|
| /Linux-v5.10/Documentation/devicetree/bindings/usb/ |
| D | mediatek,mtk-xhci.txt | 5 There are two scenarios: the first one only supports xHCI driver;
|
| /Linux-v5.10/Documentation/networking/device_drivers/ethernet/mellanox/ |
| D | mlx5.rst | 184 The tx reporter is responsible for reporting and recovering of the following two error scenarios:
211 The rx reporter is responsible for reporting and recovering of the following two error scenarios:
|
| /Linux-v5.10/Documentation/core-api/ |
| D | unaligned-memory-access.rst | 57 here; a summary of the common scenarios is presented below:
195 In summary, the 2 main scenarios where you may run into unaligned access
|
1234
