Searched refs:scenarios (Results 1 – 25 of 105) sorted by relevance
12345
| /Linux-v6.6/tools/testing/selftests/rcutorture/bin/ |
| D | config2csv.sh | 31 scenarios="`echo $scenariosarg | sed -e "s/\<CFLIST\>/$defaultconfigs/g"`"
39 for i in $scenarios
|
| D | kvm.sh | 616 }' > $T/scenarios
638 elif test "$dryrun" = scenarios
640 cat $T/scenarios
647 cp $T/scenarios $resdir/$ds/scenarios
|
| D | kvm-again.sh | 31 if ! cp "$oldrun/scenarios" $T/scenarios.oldrun
207 grep -v '^#' $T/scenarios.oldrun | awk '
|
| D | kvm-remote.sh | 121 awk < "$rundir"/scenarios -v dest="$T/bin" -v rundir="$rundir" '
243 echo " ----" System $i Batch `head -n $curbatch < "$rundir"/scenarios | tail -1` `date` 1>&2
|
| /Linux-v6.6/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::
252 Files pertaining to all scenarios in a run reside in the top-level
284 As of v5.4, a successful run with the default set of scenarios produces
342 the desired rcutorture scenarios across the available systems can be
364 The kvm.sh ``--dryrun scenarios`` argument is useful for working out
365 how many scenarios may be run in one batch across a group of systems.
|
| /Linux-v6.6/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-v6.6/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-v6.6/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 | cross-thread-rsb.rst | 58 Attack scenarios
|
| /Linux-v6.6/drivers/cpuidle/ |
| D | Kconfig | 82 host via halt_poll_ns for some scenarios).
|
| /Linux-v6.6/lib/ |
| D | Kconfig.kmsan | 56 Test suite for KMSAN, testing various error detection scenarios,
|
| D | Kconfig.kfence | 91 Test suite for KFENCE, testing various error detection scenarios with
|
| /Linux-v6.6/drivers/staging/vc04_services/interface/ |
| D | TESTING | 17 The test scenarios described in this document based on the tool vchiq_test.
|
| /Linux-v6.6/Documentation/scheduler/ |
| D | schedutil.rst | 162 - On low-load scenarios, where DVFS is most relevant, the 'running' numbers
165 - In saturated scenarios task movement will cause some transient dips,
|
| /Linux-v6.6/Documentation/networking/ |
| D | tcp-thin.rst | 11 effective. In time-dependent scenarios (like online games, control
|
| D | mptcp-sysctl.rst | 71 an high value maximize links utilization on edge scenarios e.g. lossy
|
| /Linux-v6.6/drivers/pinctrl/ |
| D | pinctrl-pistachio.c | 78 const int *scenarios; member
505 .scenarios = pistachio_##_name##_scenarios, \
970 if (pf->scenarios) { in pistachio_pinmux_enable()
972 if (pf->scenarios[i] == group) in pistachio_pinmux_enable()
|
| /Linux-v6.6/Documentation/powerpc/ |
| D | vcpudispatch_stats.rst | 11 scenarios, vcpus may be dispatched on a different processor chip (away
|
| /Linux-v6.6/Documentation/sound/hd-audio/ |
| D | dp-mst.rst | 47 So there are the following scenarios:
|
| /Linux-v6.6/Documentation/fb/ |
| D | deferred_io.rst | 34 It may be the case that this is useful in other scenarios as well. Paul Mundt
|
| /Linux-v6.6/Documentation/gpu/amdgpu/display/ |
| D | dc-debug.rst | 14 Where `N` is an integer number for some specific scenarios that the developer
|
| /Linux-v6.6/Documentation/bpf/ |
| D | prog_sk_lookup.rst | 19 BPF sk_lookup program type was introduced to address setup scenarios where
|
| /Linux-v6.6/Documentation/admin-guide/pm/ |
| D | strategies.rst | 49 Moreover, the two power management strategies address different usage scenarios.
|
| /Linux-v6.6/Documentation/networking/devlink/ |
| D | mlx5.rst | 138 The tx reporter is responsible for reporting and recovering of the following three error scenarios:
169 The rx reporter is responsible for reporting and recovering of the following two error scenarios:
|
12345
