| /openbmc/phosphor-power/phosphor-power-supply/test/ |
| H A D | power_supply_tests.cpp | 105 // Call to analyze() will update to present, that will trigger updating in setMissingToPresentExpects()
116 // The voltage defaults to 0, the first call to analyze should update the in setMissingToPresentExpects()
220 TEST_F(PowerSupplyTests, Analyze) in TEST_F() argument
234 psu.analyze(); in TEST_F()
260 // Each analyze() call will trigger a read of the presence GPIO. in TEST_F()
282 psu2.analyze(); in TEST_F()
311 psu2.analyze(); in TEST_F()
345 psu2.analyze(); in TEST_F()
360 psu2.analyze(); in TEST_F()
390 psu2.analyze(); in TEST_F()
[all …]
|
| /openbmc/openpower-hw-diags/ |
| H A D | main_nl.cpp | 19 * gpio or it can be loaded as an application to analyze hardware and
23 * --analyze: Analyze the hardware
36 printf(" --analyze: Analyze the hardware\n"); in main()
49 // the analyzer via command line (--analyze). in main()
53 // Either analyze (application mode) or daemon mode in main()
54 if (true == getCliOption(argv, argv + argc, "--analyze")) in main()
56 // Analyze the host hardware. in main()
|
| H A D | main.cpp | 13 * gpio or it will be loaded as an application to analyze hardware and
17 * --analyze: Analyze the hardware
40 printf(" --analyze: Analyze the hardware\n"); in main()
56 // the analyzer via command line (--analyze). in main()
60 // Either analyze (application mode) or daemon mode in main()
61 if (true == getCliOption(argv, argv + argc, "--analyze")) in main()
63 // Analyze the host hardware. in main()
|
| /openbmc/qemu/scripts/ |
| H A D | analyze-inclusions | 79 analyze() {
86 analyze ../include/qemu/osdep.h
89 analyze -include ../include/qemu/osdep.h ../include/hw/hw.h
92 analyze -include ../include/qemu/osdep.h trace/generated-tracers.h
95 analyze -DCOMPILING_PER_TARGET -I../target/i386 -Ii386-softmmu -include ../include/qemu/osdep.h ../…
98 analyze -DCOMPILING_PER_TARGET -I../target/i386 -Ii386-softmmu -include ../include/qemu/osdep.h ../…
|
| /openbmc/witherspoon-pfault-analysis/ |
| H A D | device_monitor.hpp | 21 * Monitors a power device for faults by calling Device::analyze()
45 timer(e, std::bind(&DeviceMonitor::analyze, this), i) in DeviceMonitor()
64 virtual void analyze() in analyze() function in witherspoon::power::DeviceMonitor
66 device->analyze(); in analyze()
|
| H A D | device.hpp | 52 * Pure virtual function to analyze an error
54 virtual void analyze() = 0;
|
| /openbmc/phosphor-power/ |
| H A D | device_monitor.hpp | 21 * Monitors a power device for faults by calling Device::analyze()
45 timer(e, std::bind(&DeviceMonitor::analyze, this), i) in DeviceMonitor()
64 virtual void analyze() in analyze() function in phosphor::power::DeviceMonitor
66 device->analyze(); in analyze()
|
| H A D | device.hpp | 52 * Pure virtual function to analyze an error
54 virtual void analyze() = 0;
|
| /openbmc/qemu/docs/devel/migration/ |
| H A D | best-practices.rst | 8 The migration stream can be analyzed thanks to ``scripts/analyze-migration.py``.
17 $ ./scripts/analyze-migration.py -f mig
24 See also ``analyze-migration.py -h`` help for more options.
|
| /openbmc/witherspoon-pfault-analysis/power-sequencer/ |
| H A D | pgood_monitor.hpp | 24 * Future commits will analyze the power sequencer chip for errors
57 void analyze() override;
62 * it will analyze the power sequencer for faults.
|
| /openbmc/linux/tools/perf/Documentation/ |
| H A D | perf-kmem.txt | 61 Analyze SLAB allocator events.
64 Analyze page allocator events
72 Only analyze samples within given time window: <start>,<stop>. Times
|
| H A D | perf-kvm.txt | 94 analyze events which occur on this vcpu. (default: all vcpus)
108 Analyze events only for given process ID(s) (comma separated list).
128 Analyze events only for given process ID(s) (comma separated list).
131 analyze events which occur on this vcpu. (default: all vcpus)
|
| H A D | perf-kwork.txt | 103 Only analyze samples within given time window: <start>,<stop>. Times
133 Only analyze samples within given time window: <start>,<stop>. Times
172 Only analyze samples within given time window: <start>,<stop>. Times
|
| /openbmc/phosphor-power/power-sequencer/ |
| H A D | pgood_monitor.hpp | 24 * Future commits will analyze the power sequencer chip for errors
57 void analyze() override;
62 * it will analyze the power sequencer for faults.
|
| H A D | mihawk-cpld.cpp | 63 // read CPLD_register error code to analyze in onFailure()
192 void MihawkCPLD::analyze() in analyze() function in phosphor::power::MihawkCPLD
207 // read CPLD_register error code to analyze and in analyze()
421 // Read CPLD_register error code and return the result to analyze.
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | python3-pyperf_2.8.1.bb | 1 SUMMARY = "A toolkit to write, run and analyze benchmarks"
3 The Python pyperf module is a toolkit to write, run and analyze benchmarks. \
|
| /openbmc/qemu/target/hexagon/ |
| H A D | gen_analyze_funcs.py | 27 ## Generate the code to analyze the instruction
63 ## Analyze the register reads
70 ## Analyze the register writes
|
| /openbmc/openbmc-tools/tof-voters/libvoters/ |
| H A D | entry_point.py | 20 import_module("libvoters.subcmd.analyze-commits"),
21 import_module("libvoters.subcmd.analyze-reviews"),
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | Parity-7.0.0 | 21 [Contribute](#contribute) software you develop, operate, or analyze with this software, including c…
31 3. You don't develop, operate, or analyze other software with it for anyone outside the team devel…
35 You may use this software to operate and analyze software you can't [contribute](#contribute) in or…
|
| /openbmc/openbmc/poky/scripts/ |
| H A D | sstate-diff-machines.sh | 35 analyze="N"
58 --analyze
87 --analyze)
88 analyze="Y"
168 if [ "${analyze}" = "Y" ] ; then
|
| /openbmc/openbmc-tools/tof-voters/ |
| H A D | README.md | 15 ./voters analyze-commits --before "2022-01-01" --after "2021-06-30"
16 ./voters analyze-reviews --before "2022-01-01" --after "2021-06-30"
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-kernel/pm-graph/ |
| H A D | pm-graph_5.13.bb | 14 # Apart from the listed RDEPENDS, analyze-suspend depends on some features
33 RPROVIDES:${PN} = "analyze-suspend"
|
| /openbmc/openbmc-tools/tof-voters/libvoters/subcmd/ |
| H A D | report.py | 21 print("Missing commits.json; run analyze-commits?")
25 print("Missing reviews.json; run analyze-reviews?")
|
| /openbmc/phosphor-objmgr/fail-monitor/ |
| H A D | monitor.hpp | 15 * This class will analyze a unit to see if it is in the failed
60 void analyze();
|
| /openbmc/sdbusplus/include/sdbusplus/message/ |
| H A D | read.hpp | 485 * @tparam Arg - The argument to analyze for grouping.
495 * @tparam Arg - The argument to analyze for grouping.
505 * @tparam Arg - The argument to analyze for grouping.
506 * @tparam Rest - The remaining arguments left to analyze.
516 * @tparam Arg - The argument to analyze for grouping.
517 * @tparam Rest - The remaining arguments left to analyze.
|