Searched full:scenarios (Results 1 – 25 of 624) sorted by relevance
12345678910>>...25
| /kernel/linux/linux-6.6/tools/testing/selftests/rcutorture/bin/ |
| D | config2csv.sh | 9 # By default, this script will take the list of scenarios from the CFLIST
10 # file in that directory, otherwise it will consider only the scenarios
13 # output file. Note that "CFLIST" is a synonym for all the scenarios in the
14 # CFLIST file, which allows easy comparison of those scenarios with selected
15 # scenarios such as BUSTED that are normally omitted from CFLIST files.
31 scenarios="`echo $scenariosarg | sed -e "s/\<CFLIST\>/$defaultconfigs/g"`"
39 for i in $scenarios
|
| D | kvm-remote.sh | 121 awk < "$rundir"/scenarios -v dest="$T/bin" -v rundir="$rundir" '
127 scenarios = "";
129 scenarios = scenarios " " $i;
130 print "kvm-test-1-run-batch.sh" scenarios >> fn;
243 echo " ----" System $i Batch `head -n $curbatch < "$rundir"/scenarios | tail -1` `date` 1>&2
249 # Launch all the scenarios.
250 nbatches="`wc -l "$rundir"/scenarios | awk '{ print $1 }'`"
267 # Wait for all remaining scenarios to complete and collect results.
|
| D | kvm-again.sh | 31 if ! cp "$oldrun/scenarios" $T/scenarios.oldrun
207 grep -v '^#' $T/scenarios.oldrun | awk '
|
| D | kvm.sh | 71 echo " --dryrun batches|scenarios|sched|script"
144 checkarg --dryrun "batches|sched|script" $# "$2" 'batches\|scenarios\|sched\|script' '^--'
616 }' > $T/scenarios
638 elif test "$dryrun" = scenarios
640 cat $T/scenarios
647 cp $T/scenarios $resdir/$ds/scenarios
|
| /kernel/linux/linux-6.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.
|
| /kernel/linux/linux-5.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
|
| /kernel/linux/linux-6.6/drivers/net/wireless/intel/iwlwifi/fw/api/ |
| D | sf.h | 39 /* SF Scenarios timers for default configuration (aligned to 32 uSec) */
51 /* SF Scenarios timers for BSS MAC configuration (aligned to 32 uSec) */
|
| /kernel/linux/linux-6.6/drivers/staging/vc04_services/interface/ |
| D | TESTING | 17 The test scenarios described in this document based on the tool vchiq_test.
36 * Scenarios
|
| /kernel/linux/linux-6.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.
|
| /kernel/linux/linux-5.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.
|
| /kernel/linux/linux-6.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.
|
| /kernel/linux/linux-5.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.
|
| /kernel/linux/linux-5.10/Documentation/livepatch/ |
| D | system-state.rst | 82 3. Supported scenarios
87 scenarios:
|
| /kernel/linux/linux-6.6/Documentation/livepatch/ |
| D | system-state.rst | 82 3. Supported scenarios
87 scenarios:
|
| /kernel/linux/linux-5.10/drivers/net/wireless/intel/iwlwifi/fw/api/ |
| D | sf.h | 95 /* SF Scenarios timers for default configuration (aligned to 32 uSec) */
107 /* SF Scenarios timers for BSS MAC configuration (aligned to 32 uSec) */
|
| /kernel/linux/linux-5.10/Documentation/ABI/obsolete/ |
| D | sysfs-class-dax | 15 what fault scenarios are supported.
|
| /kernel/linux/linux-6.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,
|
| /kernel/linux/linux-6.6/drivers/net/wireless/intel/iwlwifi/mvm/ |
| D | sf.c | 42 * Aging and idle timeouts for the different possible scenarios
70 * Aging and idle timeouts for the different possible scenarios
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/timer/ |
| D | andestech,atcpit100-timer.txt | 10 multi-function timer and provide the following usage scenarios:
|
| /kernel/linux/linux-5.10/drivers/cpuidle/ |
| D | Kconfig | 72 host via halt_poll_ns for some scenarios).
|
| /kernel/linux/linux-6.6/drivers/cpuidle/ |
| D | Kconfig | 82 host via halt_poll_ns for some scenarios).
|
| /kernel/linux/linux-5.10/include/uapi/linux/ |
| D | kexec.h | 12 /* kexec flags for different usage scenarios */
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/haswell/ |
| D | frontend.json | 136 …elivering uops. Microcode assists are used for complex instructions or scenarios that can't be ha…
186 …code sequencer. Microcode assists are used for complex instructions or scenarios that can't be ha…
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/haswellx/ |
| D | frontend.json | 136 …elivering uops. Microcode assists are used for complex instructions or scenarios that can't be ha…
186 …code sequencer. Microcode assists are used for complex instructions or scenarios that can't be ha…
|
| /kernel/linux/linux-6.6/include/uapi/linux/ |
| D | kexec.h | 12 /* kexec flags for different usage scenarios */
|
12345678910>>...25