| /openbmc/libmctp/tests/ |
| H A D | test_serial.c | 75 struct serial_test scenario[2]; in main() local
112 scenario[0].mctp = mctp_init(); in main()
113 assert(scenario[0].mctp); in main()
114 scenario[0].binding.serial = mctp_serial_init(); in main()
115 assert(scenario[0].binding.serial); in main()
116 a = &scenario[0].binding; in main()
121 mctp_register_bus(scenario[0].mctp, mctp_binding_serial_core(a->serial), in main()
125 scenario[1].mctp = mctp_init(); in main()
126 assert(scenario[1].mctp); in main()
127 mctp_set_rx_all(scenario[1].mctp, rx_message, NULL); in main()
[all …]
|
| H A D | test_i2c.c | 219 struct i2c_test scenario[2]; in main() local
220 struct i2c_test *tx_test = &scenario[0]; in main()
221 struct i2c_test *rx_test = &scenario[1]; in main()
225 memset(scenario, 0x0, sizeof(scenario)); in main()
242 mctp_i2c_setup(tx_test->i2c, I2C_ADDR_A, test_i2c_tx, scenario); in main()
252 mctp_set_rx_all(rx_test->mctp, test_i2c_rxmsg, scenario); in main()
|
| /openbmc/qemu/tests/migration/guestperf/ |
| H A D | engine.py | 109 def _migrate(self, hardware, scenario, src, dst, connect_uri): argument
132 if scenario._auto_converge:
139 cpu_throttle_increment=scenario._auto_converge_step)
141 if scenario._post_copy:
154 max_bandwidth=scenario._bandwidth * 1024 * 1024)
157 downtime_limit=scenario._downtime)
159 if scenario._compression_mt:
166 compress_threads=scenario._compression_mt_threads)
173 decompress_threads=scenario._compression_mt_threads)
175 if scenario._compression_xbzrle:
[all …]
|
| H A D | plot.py | 500 scenario = report._scenario
561 """ % (scenario._downtime, scenario._bandwidth,
562 scenario._max_iters, scenario._max_time,
563 "yes" if scenario._pause else "no", scenario._pause_iters,
564 "yes" if scenario._post_copy else "no", scenario._post_copy_iters,
565 "yes" if scenario._auto_converge else "no", scenario._auto_converge_step,
566 "yes" if scenario._compression_mt else "no", scenario._compression_mt_threads,
567 "yes" if scenario._compression_xbzrle else "no", scenario._compression_xbzrle_cache))
|
| H A D | shell.py | 31 from guestperf.scenario import Scenario
184 scenario = self.get_scenario(args)
187 report = engine.run(hardware, scenario)
224 for scenario in comparison._scenarios:
225 name = os.path.join(comparison._name, scenario._name)
235 filename = os.path.join(dirname, scenario._name + ".json")
238 report = engine.run(hardware, scenario)
|
| H A D | report.py | 23 from guestperf.scenario import Scenario
31 scenario, argument
44 self._scenario = scenario
|
| H A D | comparison.py | 20 from guestperf.scenario import Scenario
|
| /openbmc/linux/arch/arm/probes/kprobes/ |
| H A D | test-core.c | 1021 static unsigned long test_context_cpsr(int scenario) in test_context_cpsr() argument
1028 cpsr = (scenario & 0xf) << 28; /* N,Z,C,V flags */ in test_context_cpsr()
1029 cpsr |= (scenario & 0xf) << 16; /* GE flags */ in test_context_cpsr()
1030 cpsr |= (scenario & 0x1) << 27; /* Toggle Q flag */ in test_context_cpsr()
1037 if (scenario == 15) in test_context_cpsr()
1047 if (scenario == 15) in test_context_cpsr()
1052 unsigned x = (scenario >> 4); in test_context_cpsr()
1060 if ((scenario & 0xf) == 0xf) in test_context_cpsr()
1075 switch (scenario) { in test_context_cpsr()
1099 int scenario = test_case_run_count>>1; in setup_test_context() local
[all …]
|
| /openbmc/linux/tools/testing/selftests/rcutorture/bin/ |
| H A D | kvm-test-1-run-batch.sh | 26 echo Bad scenario name: \"$i\" 1>&2
78 affinity_export="`awk -f $T/cpubatches.awk -v cpu_count="$cpu_count" -v scenario=$i < /dev/null`"
|
| /openbmc/linux/Documentation/RCU/ |
| H A D | torture.rst | 195 eight-CPU scenario::
211 Note that --gdb limits you to one scenario per kvm.sh run and requires
253 directory (2020.01.20-15.54.23 in the example above), while per-scenario
254 files reside in a subdirectory named after the scenario (for example,
255 "TREE04"). If a given scenario ran more than once (as in "--configs
257 subsequent runs of that scenario include a sequence number, for example,
264 The most frequently used files in each per-scenario-run directory are:
270 This contains build output for a specific scenario.
273 This contains the console output for a specific scenario.
357 This will build each default scenario's kernel on the local system, then
[all …]
|
| /openbmc/openbmc-test-automation/redfish/managers/ |
| H A D | test_bmc_network_mac.robot | 49 # MAC address scenario
57 # MAC address scenario
88 # invalid_MAC scenario
118 # MAC address scenario
|
| /openbmc/phosphor-pid-control/notimpl/ |
| H A D | README | 2 write-only object in whatever scenario.
|
| /openbmc/linux/Documentation/crypto/ |
| H A D | devel-algos.rst | 183 ^ | | at all in this scenario.
189 ^ | | at all in this scenario.
206 .setkey() -> .init() -> .update() -> .export() at all in this scenario.
215 ^ | | at all in this scenario.
|
| /openbmc/docs/designs/ |
| H A D | power-recovery.md | 28 run services in this scenario.
30 A brownout is another scenario that commonly utilizes automated power-on
31 recovery features. A brownout is a scenario where BMC firmware detects (or is
38 brownout scenario. A UPS has a limited amount of power so it's main purpose is
103 this scenario after a BMC reboot, chassis-state-manager will check to see what
156 entire system is imminent(i.e. a blackout scenario where BMC will also lose
268 scenario is present when the system can no longer remain on.
273 Similar to the above brownout scenario, phosphor-state-manager will ensure
|
| /openbmc/u-boot/doc/ |
| H A D | README.omap-ulpi-viewport | 22 Ex: scenario:
|
| /openbmc/openbmc/poky/meta/recipes-core/busybox/busybox/ |
| H A D | makefile-libbb-race.patch | 4 This patch avoids this scenario by building libbb as the last directory.
|
| /openbmc/linux/Documentation/driver-api/mmc/ |
| H A D | mmc-async-req.rst | 70 request. The host driver may optimize for this scenario to minimize
75 Pseudocode to handle is_first_req scenario with minimal prepare overhead::
|
| /openbmc/linux/Documentation/driver-api/memory-devices/ |
| H A D | ti-gpmc.rst | 35 in time or in cycles, provision to handle this scenario has been
38 in timing structure, in this scenario, try to correlate peripheral
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/raptor2/raptor2/ |
| H A D | 0001-Remove-the-access-to-entities-checked-private-symbol.patch | 10 scenario.
|
| /openbmc/qemu/docs/devel/migration/ |
| H A D | mapped-ram.rst | 54 that's the ideal scenario for mapped-ram migration. Not having to
69 mapped-ram in this scenario is portability since background-snapshot
|
| /openbmc/linux/Documentation/admin-guide/hw-vuln/ |
| H A D | srso.rst | 8 known scenario of poisoning CPU functional units - the Branch Target
102 Mitigation addressing the cloud provider scenario - the Guest->Host
|
| /openbmc/linux/Documentation/networking/ |
| H A D | ipsec.rst | 45 above scenario. The consequence of doing so is small packet(uncompressed)
|
| /openbmc/openbmc/meta-security/recipes-ids/suricata/files/ |
| H A D | CVE-2024-37151.patch | 11 A logic error lead to the following scenario:
|
| /openbmc/openbmc/poky/meta/recipes-bsp/alsa-state/ |
| H A D | alsa-state.bb | 7 SUMMARY = "Alsa scenario files to enable alsa state restoration"
|
| /openbmc/linux/Documentation/admin-guide/mm/ |
| H A D | soft-dirty.rst | 34 there is still a scenario when we can lose soft dirty bits -- a task
|