Home
last modified time | relevance | path

Searched full:scenarios (Results 1 – 25 of 326) sorted by relevance

12345678910>>...14

/linux/tools/testing/selftests/rcutorture/bin/
H A Dconfig2csv.sh9 # 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
H A Dkvm-remote.sh121 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;
249 echo " ----" System $i Batch `head -n $curbatch < "$rundir"/scenarios | tail -1` `date` 1>&2
255 # Launch all the scenarios.
256 nbatches="`wc -l "$rundir"/scenarios | awk '{ print $1 }'`"
273 # Wait for all remaining scenarios to complete and collect results.
H A Dkvm-again.sh31 if ! cp "$oldrun/scenarios" $T/scenarios.oldrun
207 grep -v '^#' $T/scenarios.oldrun | awk '
H A Dkvm.sh74 echo " --dryrun batches|scenarios|sched|script"
157 checkarg --dryrun "batches|sched|script" $# "$2" 'batches\|scenarios\|sched\|script' '^--'
622 }' > $T/scenarios
644 elif test "$dryrun" = scenarios
646 cat $T/scenarios
653 cp $T/scenarios $resdir/$ds/scenarios
H A Dtorture.sh42 # Configurations/scenarios.
752 echo " Scenarios with .config errors: `wc -l "$T/configerrors" | awk '{ print $1 }'`"
757 echo " Scenarios with build errors: `wc -l "$T/builderrors" | awk '{ print $1 }'`"
806 # vmlinux files from corresponding scenarios.
807 echo Linking vmlinux.xz files to re-use scenarios `date` | tee -a "$tdir/log-xz" | tee -a $T/log
/linux/tools/sched_ext/
H A DREADME.md18 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/drivers/net/wireless/intel/iwlwifi/fw/api/
H A Dsf.h39 /* SF Scenarios timers for default configuration (aligned to 32 uSec) */
51 /* SF Scenarios timers for BSS MAC configuration (aligned to 32 uSec) */
/linux/Documentation/devicetree/bindings/pinctrl/
H A Dpinctrl-palmas.txt43 scenarios. So for GPIO7 if ti,palmas-override-powerhold is set
46 power off scenarios the driver will over ride the mux value.
/linux/Documentation/admin-guide/hw-vuln/
H A Dl1tf.rst65 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/Documentation/livepatch/
H A Dsystem-state.rst82 3. Supported scenarios
87 scenarios:
/linux/Documentation/scheduler/
H A Dschedutil.rst161 - On low-load scenarios, where DVFS is most relevant, the 'running' numbers
164 - In saturated scenarios task movement will cause some transient dips,
/linux/drivers/net/wireless/intel/iwlwifi/mvm/
H A Dsf.c42 * Aging and idle timeouts for the different possible scenarios
70 * Aging and idle timeouts for the different possible scenarios
/linux/drivers/cpuidle/
H A DKconfig82 host via halt_poll_ns for some scenarios).
/linux/lib/
H A DKconfig.kmsan47 Test suite for KMSAN, testing various error detection scenarios,
H A DKconfig.kfence91 Test suite for KFENCE, testing various error detection scenarios with
/linux/Documentation/networking/
H A Dtcp-thin.rst11 effective. In time-dependent scenarios (like online games, control
/linux/Documentation/arch/x86/
H A Dmds.rst104 As a special quirk to address virtualization scenarios where the host has
127 scenarios where the host has the updated microcode but the
/linux/include/uapi/linux/
H A Dkexec.h12 /* kexec flags for different usage scenarios */
/linux/tools/perf/pmu-events/arch/x86/haswellx/
H A Dfrontend.json153 …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/tools/perf/pmu-events/arch/x86/haswell/
H A Dfrontend.json153 …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/Documentation/devicetree/bindings/iio/afe/
H A Dvoltage-divider.yaml47 useful in scenarios wherein an ADC has an analog frontend,
/linux/Documentation/devicetree/bindings/display/sprd/
H A Dsprd,display-subsystem.yaml19 For different display scenarios, dpu0 and dpu1 maybe binding to different
/linux/Documentation/arch/powerpc/
H A Dvcpudispatch_stats.rst11 scenarios, vcpus may be dispatched on a different processor chip (away
/linux/Documentation/driver-api/cxl/platform/acpi/
H A Dsrat.rst24 mapping is not guaranteed. There are scenarios where "Proximity Domain 4" may
/linux/Documentation/virt/kvm/x86/
H A Drunning-nested-guests.rst56 There are several scenarios where nested KVM can be useful, to name a
203 scenarios should work even on AMD systems:

12345678910>>...14