| /linux/tools/testing/selftests/rcutorture/bin/ |
| H A 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
|
| H A 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;
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 D | kvm-again.sh | 31 if ! cp "$oldrun/scenarios" $T/scenarios.oldrun
207 grep -v '^#' $T/scenarios.oldrun | awk '
|
| H A D | kvm.sh | 74 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
|
| /linux/Documentation/RCU/ |
| H A 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 ma
[all...] |
| /linux/tools/sched_ext/ |
| H A 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/drivers/net/wireless/intel/iwlwifi/fw/api/ |
| H A 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/Documentation/devicetree/bindings/pinctrl/ |
| H A 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/Documentation/admin-guide/hw-vuln/ |
| H A 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/drivers/staging/vc04_services/interface/ |
| H A D | TESTING | 17 The test scenarios described in this document based on the tool vchiq_test.
36 * Scenarios
|
| /linux/Documentation/livepatch/ |
| H A D | system-state.rst | 82 3. Supported scenarios
87 scenarios:
|
| /linux/Documentation/scheduler/ |
| H A 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/drivers/net/wireless/intel/iwlwifi/mvm/ |
| H A D | sf.c | 42 * Aging and idle timeouts for the different possible scenarios
70 * Aging and idle timeouts for the different possible scenarios
|
| /linux/Documentation/driver-api/ |
| H A D | extcon.rst | 52 scenarios by providing a standardized way to report and query connector
109 scenarios like a single port that can either be USB or HDMI, but not both
|
| /linux/drivers/cpuidle/ |
| H A D | Kconfig | 82 host via halt_poll_ns for some scenarios).
|
| /linux/lib/ |
| H A D | Kconfig.kmsan | 56 Test suite for KMSAN, testing various error detection scenarios,
|
| H A D | Kconfig.kfence | 91 Test suite for KFENCE, testing various error detection scenarios with
|
| /linux/include/uapi/linux/ |
| H A D | kexec.h | 12 /* kexec flags for different usage scenarios */
|
| /linux/Documentation/networking/ |
| H A D | tcp-thin.rst | 11 effective. In time-dependent scenarios (like online games, control
|
| /linux/Documentation/arch/x86/ |
| H A 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/Documentation/networking/devlink/ |
| H A D | mlx5.rst | 145 The tx reporter is responsible for reporting and recovering of the following three error scenarios:
176 The rx reporter is responsible for reporting and recovering of the following two error scenarios:
|
| /linux/Documentation/devicetree/bindings/iio/afe/ |
| H A D | voltage-divider.yaml | 47 useful in scenarios wherein an ADC has an analog frontend,
|
| /linux/Documentation/gpu/amdgpu/display/ |
| H A D | dcn-overview.rst | 186 configuration parameters for multiple scenarios supported by our hardware.
195 (Note: There are many scenarios when DC will decide to reserve extra pipes
|
| /linux/tools/perf/pmu-events/arch/x86/haswell/ |
| H A D | frontend.json | 153 "PublicDescription": "This event counts cycles during which the microcode sequencer assisted the Front-end in delivering uops. Microcode assists are used for complex instructions or scenarios that can't be handled by the standard decoder. Using other instructions, if possible, will usually improve performance.",
209 "PublicDescription": "This event counts uops delivered by the Front-end with the assistance of the microcode sequencer. Microcode assists are used for complex instructions or scenarios that can't be handled by the standard decoder. Using other instructions, if possible, will usually improve performance.",
|
| /linux/arch/x86/lib/ |
| H A D | copy_mc.c | 55 * corner case poison consumption scenarios, For example, accessing
|