Home
last modified time | relevance | path

Searched refs:scenarios (Results 1 – 25 of 175) sorted by relevance

1234567

/openbmc/qemu/tests/migration/guestperf/
H A Dcomparison.py23 def __init__(self, name, scenarios): argument
25 self._scenarios = scenarios
30 Comparison("pause-iters", scenarios = [
44 Comparison("post-copy-bandwidth", scenarios = [
60 Comparison("post-copy-iters", scenarios = [
74 Comparison("auto-converge-iters", scenarios = [
86 Comparison("auto-converge-bandwidth", scenarios = [
102 Comparison("compr-mt", scenarios = [
114 Comparison("compr-xbzrle", scenarios = [
128 Comparison("compr-multifd", scenarios = [
[all …]
/openbmc/linux/tools/testing/selftests/rcutorture/bin/
H A Dconfig2csv.sh31 scenarios="`echo $scenariosarg | sed -e "s/\<CFLIST\>/$defaultconfigs/g"`"
39 for i in $scenarios
H A Dkvm.sh616 }' > $T/scenarios
638 elif test "$dryrun" = scenarios
640 cat $T/scenarios
647 cp $T/scenarios $resdir/$ds/scenarios
H A Dkvm-again.sh31 if ! cp "$oldrun/scenarios" $T/scenarios.oldrun
207 grep -v '^#' $T/scenarios.oldrun | awk '
H A Dkvm-remote.sh121 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
/openbmc/linux/Documentation/RCU/
H A Dtorture.rst178 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.
/openbmc/openbmc-test-automation/openpower/ras/
H A Dtest_sanity_ecmd.robot2 Documentation Test RAS sanity scenarios using ecmd commands.
H A Dtest_sanity.robot2 Documentation Test RAS sanity scenarios.
/openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python3-mlcommons-loadgen/
H A Dpython3-mlcommons-loadgen_5.0.5.bb4 traffic for scenarios as formulated by a diverse set of experts \
/openbmc/u-boot/doc/device-tree-bindings/timer/
H A Datcpit100_timer.txt10 multi-function timer and provide the following usage scenarios:
/openbmc/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.
/openbmc/openbmc/poky/meta/recipes-extended/zstd/
H A Dzstd_1.5.6.bb3 real-time compression scenarios at zlib-level and better compression ratios. \
/openbmc/openbmc/meta-openpower/classes/
H A Dopenpower-software-manager-virtual-pnor.bbclass13 # To handle warm reboot scenarios, the checking and clearing of
/openbmc/qemu/docs/devel/migration/
H A Dqatzip-compression.rst4 In scenarios with limited network bandwidth, the ``QATzip`` solution can help
165 3 - For other scenarios, use the ``QPL`` method first.
/openbmc/u-boot/doc/uImage.FIT/
H A Dcommand_syntax_extensions.txt10 scenarios, and then introduces new argument syntax.
13 bootm usage scenarios
16 Below is a summary of bootm usage scenarios, focused on booting a PowerPC
/openbmc/linux/Documentation/livepatch/
H A Dsystem-state.rst82 3. Supported scenarios
87 scenarios:
/openbmc/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.
/openbmc/linux/Documentation/scheduler/
H A Dschedutil.rst162 - On low-load scenarios, where DVFS is most relevant, the 'running' numbers
165 - In saturated scenarios task movement will cause some transient dips,
/openbmc/openbmc/poky/meta/recipes-connectivity/kea/files/
H A Dfix-multilib-conflict.patch52 // // options and fields to uniquely identify a client. Those scenarios
/openbmc/entity-manager/configurations/
H A DVENDORS.md34 These guidelines are not meant to be exhaustive rules to cover all scenarios and
/openbmc/linux/drivers/staging/vc04_services/interface/
H A DTESTING17 The test scenarios described in this document based on the tool vchiq_test.
/openbmc/linux/lib/
H A DKconfig.kmsan56 Test suite for KMSAN, testing various error detection scenarios,
/openbmc/linux/drivers/cpuidle/
H A DKconfig82 host via halt_poll_ns for some scenarios).
/openbmc/docs/designs/
H A Dbmc-reset-with-host-up.md12 and a variety of different error scenarios. When the BMC is rebooted while the
157 shutdown scenarios. To handle different host crash scenarios, the register will
/openbmc/linux/drivers/pinctrl/
H A Dpinctrl-pistachio.c78 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()

1234567