Searched full:scenarios (Results 1 – 25 of 409) sorted by relevance
12345678910>>...17
/linux-6.12.1/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 | 73 echo " --dryrun batches|scenarios|sched|script" 155 checkarg --dryrun "batches|sched|script" $# "$2" 'batches\|scenarios\|sched\|script' '^--' 627 }' > $T/scenarios 649 elif test "$dryrun" = scenarios 651 cat $T/scenarios 658 cp $T/scenarios $resdir/$ds/scenarios
|
D | torture.sh | 33 # Configurations/scenarios. 632 echo " Scenarios with .config errors: `wc -l "$T/configerrors" | awk '{ print $1 }'`" 637 echo " Scenarios with build errors: `wc -l "$T/builderrors" | awk '{ print $1 }'`" 686 # vmlinux files from corresponding scenarios. 687 echo Linking vmlinux.xz files to re-use scenarios `date` | tee -a "$tdir/log-xz" | tee -a $T/log
|
/linux-6.12.1/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 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-6.12.1/tools/sched_ext/ |
D | README.md | 18 types of workloads or scenarios they're designed to accommodate, and whether or 161 useful in limited scenarios, they are not intended to be practical. 171 Though very simple, in limited scenarios, this scheduler can perform reasonably 203 Similar to scx_simple, in limited scenarios, this scheduler can perform
|
/linux-6.12.1/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) */
|
/linux-6.12.1/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-6.12.1/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.
|
/linux-6.12.1/drivers/staging/vc04_services/interface/ |
D | TESTING | 17 The test scenarios described in this document based on the tool vchiq_test. 36 * Scenarios
|
/linux-6.12.1/Documentation/livepatch/ |
D | system-state.rst | 82 3. Supported scenarios 87 scenarios:
|
/linux-6.12.1/Documentation/scheduler/ |
D | schedutil.rst | 161 - On low-load scenarios, where DVFS is most relevant, the 'running' numbers 164 - In saturated scenarios task movement will cause some transient dips,
|
/linux-6.12.1/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
|
/linux-6.12.1/drivers/cpuidle/ |
D | Kconfig | 82 host via halt_poll_ns for some scenarios).
|
/linux-6.12.1/include/uapi/linux/ |
D | kexec.h | 12 /* kexec flags for different usage scenarios */
|
/linux-6.12.1/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-6.12.1/Documentation/networking/devlink/ |
D | mlx5.rst | 142 The tx reporter is responsible for reporting and recovering of the following three error scenarios: 173 The rx reporter is responsible for reporting and recovering of the following two error scenarios:
|
/linux-6.12.1/Documentation/networking/ |
D | tcp-thin.rst | 11 effective. In time-dependent scenarios (like online games, control
|
/linux-6.12.1/Documentation/arch/x86/ |
D | mds.rst | 104 As a special quirk to address virtualization scenarios where the host has 127 scenarios where the host has the updated microcode but the
|
/linux-6.12.1/Documentation/devicetree/bindings/iio/afe/ |
D | voltage-divider.yaml | 47 useful in scenarios wherein an ADC has an analog frontend,
|
/linux-6.12.1/tools/perf/pmu-events/arch/x86/haswellx/ |
D | frontend.json | 153 …elivering uops. Microcode assists are used for complex instructions or scenarios that can't be ha… 209 …code sequencer. Microcode assists are used for complex instructions or scenarios that can't be ha…
|
/linux-6.12.1/tools/perf/pmu-events/arch/x86/haswell/ |
D | frontend.json | 153 …elivering uops. Microcode assists are used for complex instructions or scenarios that can't be ha… 209 …code sequencer. Microcode assists are used for complex instructions or scenarios that can't be ha…
|
/linux-6.12.1/Documentation/gpu/amdgpu/display/ |
D | dcn-overview.rst | 184 configuration parameters for multiple scenarios supported by our hardware. 193 (Note: There are many scenarios when DC will decide to reserve extra pipes
|
12345678910>>...17